Description of problem: Running Fedora rawhide /usr/sbin/init under moby-engine fail. Version-Release number of selected component (if applicable): registry.fedoraproject.org/fedora rawhide ee44c24ba5eb 11 hours ago 175MB systemd-246.6-3.fc34.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. Have Dockerfile: FROM registry.fedoraproject.org/fedora:rawhide RUN dnf install -y /usr/sbin/init ENTRYPOINT [ "/usr/sbin/init" ] 2. Built the image: docker build -t system-rawhide . 3. Run the container: docker run --tmpfs /run -v /sys/fs/cgroup:/sys/fs/cgroup:ro --rm -ti systemd-rawhide Actual results: systemd v246.6-3.fc34 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified) Detected virtualization container-other. Detected architecture x86-64. Welcome to Fedora 34 (Container Image Prerelease)! Set hostname to <a2c559ab2784>. Failed to create /system.slice/docker-a2c559ab278447649e00d64e8f361e1f8c26ed7f8517cc335444b36e7de3dad6.scope/init.scope control group: Operation not permitted Failed to allocate manager object: Operation not permitted [!!!!!!] Failed to allocate manager object. Exiting PID 1... Expected results: systemd v246.6-3.fc33 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified) Detected virtualization container-other. Detected architecture x86-64. Welcome to Fedora 33 (Container Image)! Set hostname to <f96d24152c03>. Queued start job for default target Graphical Interface. [ OK ] Created slice system-getty.slice. [ OK ] Created slice system-modprobe.slice. [ OK ] Created slice User and Session Slice. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Reached target Network is Online. [ OK ] Reached target Paths. [ OK ] Reached target Remote File Systems. [ OK ] Reached target Slices. [ OK ] Reached target Swap. [ OK ] Listening on Process Core Dump Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [...] Additional info: The expected output is from the same Dockerfile, just changing rawhide to 33. This is with moby-engine-19.03.11-1.ce.git42e35e6.fc32.x86_64, and with host booted with systemd.unified_cgroup_hierarchy=0. The weird thing is that the systemd version installed on Fedora 33 and Fedora rawhide are the same (v246.6-3), only the %dist is different.
This rawhide-systemd-based container workload also started to fail on GitHub Actions hosts at the same time: https://github.com/freeipa/freeipa-container/runs/1394189730?
This issue is potentially related to change done in bug 1869030.
Also note bug 1900021.
Also bug 1897839 and https://github.com/moby/moby/issues/41704 seems related.
So far, such issues with docker were usually because docker was not setting up cgroups properly. I don't know much about docker so the issue will have to be investigated by someone else.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.