{"action":"created","issue":{"url":"https://api.github.com/repos/fedora-cloud/docker-brew-fedora/issues/21","labels_url":"https://api.github.com/repos/fedora-cloud/docker-brew-fedora/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/fedora-cloud/docker-brew-fedora/issues/21/comments","events_url":"https://api.github.com/repos/fedora-cloud/docker-brew-fedora/issues/21/events","html_url":"https://github.com/fedora-cloud/docker-brew-fedora/issues/21","id":106948757,"number":21,"title":"Regression in fedora:22 over fedora:21 when running systemd in the container","user":{"login":"adelton","id":2536912,"avatar_url":"https://avatars.githubusercontent.com/u/2536912?v=3","gravatar_id":"","url":"https://api.github.com/users/adelton","html_url":"https://github.com/adelton","followers_url":"https://api.github.com/users/adelton/followers","following_url":"https://api.github.com/users/adelton/following{/other_user}","gists_url":"https://api.github.com/users/adelton/gists{/gist_id}","starred_url":"https://api.github.com/users/adelton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adelton/subscriptions","organizations_url":"https://api.github.com/users/adelton/orgs","repos_url":"https://api.github.com/users/adelton/repos","events_url":"https://api.github.com/users/adelton/events{/privacy}","received_events_url":"https://api.github.com/users/adelton/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-17T09:50:45Z","updated_at":"2015-10-20T07:43:07Z","closed_at":null,"body":"With Fedora 21 image (e26efd418c48), following the steps from http://vpavlin.eu/2015/02/fedora-docker-and-systemd/ with Dockerfile\r\n\r\n```\r\nFROM fedora:21\r\nENV container docker\r\nRUN systemctl mask systemd-remount-fs.service dev-hugepages.mount sys-fs-fuse-connections.mount systemd-logind.service getty.target console-getty.service\r\nRUN cp /usr/lib/systemd/system/dbus.service /etc/systemd/system/; sed -i 's/OOMScoreAdjust=-900//' /etc/systemd/system/dbus.service\r\nVOLUME [ \"/tmp\", \"/run\" ]\r\nCMD [ \"/usr/sbin/init\" ]\r\nLABEL RUN \"docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro ${NAME}\"\r\n```\r\n\r\nand running it with\r\n\r\n```\r\ndocker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora-21-systemd\r\n```\r\n\r\nmakes the container start without any error. For the record, the processes left running are\r\n\r\n```\r\n    1 ?        Ss     0:00 /usr/sbin/init\r\n   22 ?        Ss     0:00 /usr/lib/systemd/systemd-journald\r\n   28 ?        Ss     0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation\r\n```\r\n\r\nWhen I try to use the same Dockerfile for Fedora 22 (ded7cd95e059), I get multiple errors. The Dockerfile is\r\n\r\n```\r\nFROM fedora:22\r\nENV container docker\r\nRUN systemctl mask systemd-remount-fs.service dev-hugepages.mount sys-fs-fuse-connections.mount systemd-logind.service getty.target console-getty.service\r\nRUN cp /usr/lib/systemd/system/dbus.service /etc/systemd/system/; sed -i 's/OOMScoreAdjust=-900//' /etc/systemd/system/dbus.service\r\nVOLUME [ \"/tmp\", \"/run\" ]\r\nCMD [ \"/usr/sbin/init\" ]\r\nLABEL RUN \"docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro ${NAME}\"\r\n```\r\n\r\nI run it as\r\n\r\n```\r\ndocker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro fedora-22-systemd\r\n```\r\n\r\nand the output is\r\n\r\n```\r\nsystemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)\r\nDetected virtualization docker.\r\nDetected architecture x86-64.\r\nRunning with unpopulated /etc.\r\n\r\nWelcome to Fedora 22 (Twenty Two)!\r\n\r\nSet hostname to <be4d5fd6bb84>.\r\nInitializing machine ID from random generator.\r\nPopulated /etc with preset unit settings.\r\nRunning in a container, ignoring fstab device entry for /dev/disk/by-uuid/872ae83d-8ae9-488f-8927-0266665410ef.\r\nCannot add dependency job for unit systemd-remount-fs.service, ignoring: Unit systemd-remount-fs.service is masked.\r\nCannot add dependency job for unit sys-fs-fuse-connections.mount, ignoring: Unit sys-fs-fuse-connections.mount is masked.\r\nCannot add dependency job for unit dev-hugepages.mount, ignoring: Unit dev-hugepages.mount is masked.\r\nCannot add dependency job for unit systemd-logind.service, ignoring: Unit systemd-logind.service is masked.\r\nCannot add dependency job for unit getty.target, ignoring: Unit getty.target is masked.\r\nCannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.\r\n[  OK  ] Created slice Root Slice.\r\n[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.\r\n[  OK  ] Reached target Swap.\r\n[  OK  ] Reached target Remote File Systems.\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\nUnit systemd-journald-audit.socket entered failed state.\r\n[  OK  ] Reached target Local File Systems.\r\n[  OK  ] Created slice System Slice.\r\n[  OK  ] Reached target Slices.\r\n[  OK  ] Listening on Journal Socket.\r\n         Starting Rebuild Dynamic Linker Cache...\r\n         Starting Load/Save Random Seed...\r\n[  OK  ] Listening on Journal Socket (/dev/log).\r\n         Starting Journal Service...\r\n         Starting Rebuild Hardware Database...\r\n         Starting Rebuild Journal Catalog...\r\n[  OK  ] Listening on Delayed Shutdown Socket.\r\n[  OK  ] Reached target Paths.\r\n[  OK  ] Reached target Encrypted Volumes.\r\n         Starting First Boot Wizard...\r\n[  OK  ] Started Load/Save Random Seed.\r\nsystemd-journald.service: main process exited, code=exited, status=1/FAILURE\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\n[DEPEND] Dependency failed for Flush Journal to Persistent Storage.\r\nJob systemd-journal-flush.service/start failed with result 'dependency'.\r\nUnit systemd-journald.service entered failed state.\r\nsystemd-journald.service failed.\r\n[  OK  ] Started Rebuild Journal Catalog.\r\n[  OK  ] Started First Boot Wizard.\r\nsystemd-journald.service has no holdoff time, scheduling restart.\r\n[  OK  ] Stopped Flush Journal to Persistent Storage.\r\n[  OK  ] Stopped Journal Service.\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\n         Starting Journal Service...\r\n         Starting Create System Users...\r\nsystemd-journald.service: main process exited, code=exited, status=1/FAILURE\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\n[DEPEND] Dependency failed for Flush Journal to Persistent Storage.\r\nJob systemd-journal-flush.service/start failed with result 'dependency'.\r\nUnit systemd-journald.service entered failed state.\r\nsystemd-journald.service failed.\r\nsystemd-journald.service has no holdoff time, scheduling restart.\r\n[  OK  ] Stopped Flush Journal to Persistent Storage.\r\n[  OK  ] Stopped Journal Service.\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\n         Starting Journal Service...\r\nsystemd-journald.service: main process exited, code=exited, status=1/FAILURE\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\n[DEPEND] Dependency failed for Flush Journal to Persistent Storage.\r\nJob systemd-journal-flush.service/start failed with result 'dependency'.\r\nUnit systemd-journald.service entered failed state.\r\nsystemd-journald.service failed.\r\nsystemd-journald.service has no holdoff time, scheduling restart.\r\n[  OK  ] Stopped Flush Journal to Persistent Storage.\r\n[  OK  ] Stopped Journal Service.\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\n         Starting Journal Service...\r\n[  OK  ] Started Create System Users.\r\nsystemd-journald.service: main process exited, code=exited, status=1/FAILURE\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\n[DEPEND] Dependency failed for Flush Journal to Persistent Storage.\r\nJob systemd-journal-flush.service/start failed with result 'dependency'.\r\nUnit systemd-journald.service entered failed state.\r\nsystemd-journald.service failed.\r\nsystemd-journald.service has no holdoff time, scheduling restart.\r\n[  OK  ] Stopped Flush Journal to Persistent Storage.\r\n[  OK  ] Stopped Journal Service.\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\n         Starting Journal Service...\r\nsystemd-journald.service: main process exited, code=exited, status=1/FAILURE\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\n[DEPEND] Dependency failed for Flush Journal to Persistent Storage.\r\nJob systemd-journal-flush.service/start failed with result 'dependency'.\r\nUnit systemd-journald.service entered failed state.\r\nsystemd-journald.service failed.\r\nsystemd-journald.service has no holdoff time, scheduling restart.\r\n[  OK  ] Stopped Flush Journal to Persistent Storage.\r\n[  OK  ] Stopped Journal Service.\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\nstart request repeated too quickly for systemd-journald.service\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\n[DEPEND] Dependency failed for Flush Journal to Persistent Storage.\r\nJob systemd-journal-flush.service/start failed with result 'dependency'.\r\nUnit systemd-journald.service entered failed state.\r\nsystemd-journald.service failed.\r\n         Starting Create Volatile Files and Directories...\r\nsystemd-journald-audit.socket failed to listen on sockets: Operation not permitted\r\n[FAILED] Failed to listen on Journal Audit Socket.\r\nSee \"systemctl status systemd-journald-audit.socket\" for details.\r\nstart request repeated too quickly for systemd-journald.service\r\n[FAILED] Failed to start Journal Service.\r\nSee \"systemctl status systemd-journald.service\" for details.\r\nUnit systemd-journald.socket entered failed state.\r\nsystemd-journald.service failed.\r\n[  OK  ] Started Create Volatile Files and Directories.\r\n         Starting Update UTMP about System Boot/Shutdown...\r\n[  OK  ] Started Rebuild Dynamic Linker Cache.\r\n[  OK  ] Started Update UTMP about System Boot/Shutdown.\r\n[  OK  ] Started Rebuild Hardware Database.\r\n         Starting Update is Completed...\r\n[  OK  ] Started Update is Completed.\r\n[  OK  ] Reached target System Initialization.\r\n[  OK  ] Listening on D-Bus System Message Bus Socket.\r\n[  OK  ] Reached target Sockets.\r\n[  OK  ] Reached target Basic System.\r\n[  OK  ] Reached target Containers.\r\n[  OK  ] Started D-Bus System Message Bus.\r\n         Starting D-Bus System Message Bus...\r\n         Starting Permit User Sessions...\r\n[  OK  ] Reached target Timers.\r\nCannot add dependency job for unit systemd-remount-fs.service, ignoring: Unit systemd-remount-fs.service is masked.\r\nCannot add dependency job for unit sys-fs-fuse-connections.mount, ignoring: Unit sys-fs-fuse-connections.mount is masked.\r\nCannot add dependency job for unit dev-hugepages.mount, ignoring: Unit dev-hugepages.mount is masked.\r\n         Starting dnf makecache...\r\n         Starting Cleanup of Temporary Directories...\r\n[  OK  ] Started Permit User Sessions.\r\n[  OK  ] Reached target Multi-User System.\r\n[  OK  ] Reached target Graphical Interface.\r\n         Starting Update UTMP about System Runlevel Changes...\r\n[  OK  ] Started Cleanup of Temporary Directories.\r\n[  OK  ] Started Update UTMP about System Runlevel Changes.\r\ndnf-makecache.service: main process exited, code=exited, status=1/FAILURE\r\n[FAILED] Failed to start dnf makecache.\r\nSee \"systemctl status dnf-makecache.service\" for details.\r\nStartup finished in 4.305s.\r\nUnit dnf-makecache.service entered failed state.\r\ndnf-makecache.service failed.\r\n```\r\n\r\nThe processes running are\r\n\r\n```\r\nroot         1  0.1  0.1  43156  4888 ?        Ss   09:43   0:00 /usr/sbin/init\r\ndbus        32  0.0  0.1  52048  4032 ?        Ss   09:43   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile -\r\n```\r\n\r\nNote that the ```systemctl mask``` and ```dbus.service``` probably aren't needed with ```fedora:22``` because the services are already masked and D-Bus starts with stock configuration fine. So the minimal Dockerfile that we'd probably like to see working without any ignoring and FAILED error messages is\r\n\r\n```\r\nFROM fedora:22\r\nENV container docker\r\nVOLUME [ \"/tmp\", \"/run\" ]\r\nCMD [ \"/usr/sbin/init\" ]\r\nLABEL RUN \"docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro ${NAME}\"\r\n```"},"comment":{"url":"https://api.github.com/repos/fedora-cloud/docker-brew-fedora/issues/comments/149464634","html_url":"https://github.com/fedora-cloud/docker-brew-fedora/issues/21#issuecomment-149464634","issue_url":"https://api.github.com/repos/fedora-cloud/docker-brew-fedora/issues/21","id":149464634,"user":{"login":"praiskup","id":3277839,"avatar_url":"https://avatars.githubusercontent.com/u/3277839?v=3","gravatar_id":"","url":"https://api.github.com/users/praiskup","html_url":"https://github.com/praiskup","followers_url":"https://api.github.com/users/praiskup/followers","following_url":"https://api.github.com/users/praiskup/following{/other_user}","gists_url":"https://api.github.com/users/praiskup/gists{/gist_id}","starred_url":"https://api.github.com/users/praiskup/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/praiskup/subscriptions","organizations_url":"https://api.github.com/users/praiskup/orgs","repos_url":"https://api.github.com/users/praiskup/repos","events_url":"https://api.github.com/users/praiskup/events{/privacy}","received_events_url":"https://api.github.com/users/praiskup/received_events","type":"User","site_admin":false},"created_at":"2015-10-20T07:43:07Z","updated_at":"2015-10-20T07:43:07Z","body":"FWIW, I grabbed the latest (nightly) F22 image http://koji.fedoraproject.org/koji/taskinfo?taskID=11509864\r\nand the image boots is clean."}}