Project Atomic uses rpm-ostree to manage the host environment, so we can't install arbitrary additional packages. The Atomic host environment is also not a reasonable place to run tasks, as a lot packages simply won't be present - the Atomic host component provides the bare minimum of infrastructure needed to run containers, so a lot of otherwise expected OS components are missing. Amit's patch at http://gerrit.beaker-project.org/#/c/3199 provides a reasonable starting point towards enabling this. My suggestion is that we aim to get something basic released in the 0.18 time frame (such as Amit's patch, modified to avoid touching the public internet), and then iterate from there. The harness repo URL should be injected by the server, rather than hardcoded into the template snippet. For the initial iteration, only the Docker image registry URL needs to be configurable. The base image and whether or not the container is privileged will need to be configurable eventually, but that doesn't need to be in the initial iteration.
http://gerrit.beaker-project.org/#/c/3199/3 What it does: - Run tests inside a Fedora 20 docker container - Allows specifying a docker registry. If not specified, defaults to using the public registry - Uses restraint test harness (allows specifying the restraint repo) What it doesn't allow: - Tests cannot restart the host (trivial to add) - tests cannot spawn other containers (easy to add) - Test cannot specify the distro in which to execute the test (doable fairly easily once we have the restraint repos setup such that we can just specify a dsitro variable)
(In reply to Amit Saha from comment #1) > http://gerrit.beaker-project.org/#/c/3199/3 > What it doesn't allow: > > - Tests cannot restart the host (trivial to add) > - tests cannot spawn other containers (easy to add) > - Test cannot specify the distro in which to execute the test (doable fairly > easily once we have the restraint repos setup such that we can just specify > a dsitro variable) Instead of hardcoding the distro which the container runs and hence the test harness runs in, I now default to the distro image used in <distroRequires>. So, for example, if the distro is Fedora20, I use the docker image as Fedora with tag 20. Two additional ks_meta variables, "docker_image" and "docker_tag" can be used to specify a different distro/tag. However, the restraint repo URL *needs* to be specified correctly, since it defaults to the Fedora 20 URL. For eg: ks_meta="contained_harness docker_registry=docker-registry.mysys.com/ docker_image=centos6 docker_tag=latest restraint_repo=https://bpeck.fedorapeople.org/restraint/el6.repo selinux=--disabled" will run the test harness in CentOS6.
> - Test cannot specify the distro in which to execute the test (doable fairly > easily once we have the restraint repos setup such that we can just specify > a dsitro variable) As explained by https://git.beaker-project.org/cgit/beaker/diff/documentation/user-guide/customizing-installation.rst?h=develop, the merged patch allows selecting any arbitrary docker image for the harness with the mentioned restrictions.
Where are we at with getting restraint included in the default harness repos? That would address the issue with needed to specify the correct restraint repo.
Amit has back-ported this to release-0.18 for the 0.18.3 release.
Beaker 0.18.3 has been released.