rpm-ostree/vagrant/Dockerfile.builder

FROM centos/tools
ADD atomic-centos-continuous.repo /etc/yum.repos.d/atomic-centos-continuous.repo
RUN yum -y install yum-plugin-priorities sudo && \
    yum -y install bash bzip2 coreutils cpio diffutils system-release findutils gawk gcc gcc-c++ \
      grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux \
      which xz python gcc gperf 'pkgconfig(libsystemd)' \
    && yum-builddep -y rpm-ostree
LABEL RUN "/usr/bin/docker run --privileged -ti -v /var/roothome:/root -v /etc:/host/etc -v /usr:/host/usr \${IMAGE}"
WORKDIR /root/sync
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon 2016-06-04 17:48:06 +03:00			`FROM centos/tools`
			`ADD atomic-centos-continuous.repo /etc/yum.repos.d/atomic-centos-continuous.repo`
			`RUN yum -y install yum-plugin-priorities sudo && \`
			`yum -y install bash bzip2 coreutils cpio diffutils system-release findutils gawk gcc gcc-c++ \`
			`grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux \`
buildimg: add new prereqs Closes: #360 Approved by: cgwalters 2016-06-24 21:41:25 +03:00			`which xz python gcc gperf 'pkgconfig(libsystemd)' \`
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon 2016-06-04 17:48:06 +03:00			`&& yum-builddep -y rpm-ostree`
vagrant: set up ssh for root user From Vagrantfile: It's just easier to have ssh set up as root from the start so that tests don't need to sudo, which can sometimes cause issues. If we need to test any unprivileged things, we can still just sudo back into the vagrant user. Closes: #344 Approved by: cgwalters 2016-06-22 18:51:45 +03:00			`LABEL RUN "/usr/bin/docker run --privileged -ti -v /var/roothome:/root -v /etc:/host/etc -v /usr:/host/usr \${IMAGE}"`
			`WORKDIR /root/sync`