https://bugzilla.redhat.com/show_bug.cgi?id=1192081
Bug ID: 1192081 Summary: Modify base image Dockerfile to enable systemd to run smoothly Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5@redhat.com Reporter: vpavlin@redhat.com QA Contact: extras-qa@fedoraproject.org CC: adimania@gmail.com, admiller@redhat.com, golang@lists.fedoraproject.org, hushan.jia@gmail.com, jchaloup@redhat.com, jperrin@centos.org, lsm5@redhat.com, mattdm@redhat.com, mgoldman@redhat.com, miminar@redhat.com, s@shk.io, thrcka@redhat.com, vbatts@redhat.com
Description of problem: systemd requires container=docker set in env and /run, /tmp to be mountpoints start successfully. In my opinion, we should add
ENV container=docker VOLUME ['/run', '/tmp']
to the base image Dockerfile.
Command
docker run --it --rm -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora:rawhide /usr/sbin/init
would then be all an user would need to "boot" systemd in a container.
I've already made some changes in KS file - remove fstab and machine-id, mask mount units... which make the boot sequence smooth.
More changes to boot sequence will probably come later (f.e. switch from graphical.target to multi-user target)
I'd also like to suggest new Rawhide build to be pushed to registry. This one works for me quite well: http://koji.fedoraproject.org/koji/taskinfo?taskID=8883309