https://bugzilla.redhat.com/show_bug.cgi?id=1192081
--- Comment #12 from Jan Pazdziora <jpazdziora(a)redhat.com> ---
Dan,
what is the minimal execution environment for systemd? The ENV container=docker
that the comment 0 asks for does not seem to be present in current
fedora:rawhide, for example:
# docker run -ti --rm fedora:rawhide bash -c 'set | grep container'
BASH_EXECUTION_STRING='set | grep container'
Also the /run and /tmp VOLUMEs do not seem to be defined:
# docker run -ti --rm fedora:rawhide mount | egrep '/run|/tmp'
/dev/mapper/fedora_cloud--qe--14-root on /run/secrets type xfs
(rw,relatime,seclabel,attr2,inode64,noquota)
The net effect is that
# docker run -it --rm -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora:rawhide
/usr/sbin/init
hangs with no output produced.
Adding -e container=docker to the command line shows
# docker run -it --rm -e container=docker -v /sys/fs/cgroup:/sys/fs/cgroup:ro
fedora:rawhide /usr/sbin/init
Failed to mount tmpfs at /run: Operation not permitted
[!!!!!!] Failed to mount API filesystems, freezing.
Freezing execution.
Only another --tmpfs /run or -v /run makes systemd actually start, and adding
--tmpfs /tmp makes the error
tmp.mount: Mount process exited, code=exited status=32
[FAILED] Failed to mount Temporary Directory.
See 'systemctl status tmp.mount' for details.
tmp.mount: Unit entered failed state.
go away.
From this point of view, the current fedora:rawhide does not seem to have made
running systemd easier.
This is with
docker.io/fedora rawhide d93e998fad14 3 months ago 250.7 MB
-- if there is some newer image somewhere, having a way to test it (name/tag)
would be nice.
--
You are receiving this mail because:
You are on the CC list for the bug.