Description of problem: Attempt to run /usr/sbin/init in container fails with multiple Failed to determine whether ... is a mount point errors. Version-Release number of selected component (if applicable): docker-1.13.1-7.git14cc629.fc26.x86_64 oci-systemd-hook-0.1.7-1.git1788cf2.fc26.x86_64 selinux-policy-3.13.1-249.fc26.noarch How reproducible: Deterministic. Steps to Reproduce: 1. dnf install -y docker 2. setsebool -P container_manage_cgroup 1 3. systemctl start docker 4. docker run --rm -ti -e container=docker registry.fedoraproject.org/fedora:25 /usr/sbin/init Actual results: Failed to determine whether /sys is a mount point: Operation not permitted Failed to determine whether /proc is a mount point: Operation not permitted Failed to determine whether /dev is a mount point: Operation not permitted Failed to determine whether /dev/shm is a mount point: Operation not permitted Failed to determine whether /run is a mount point: Operation not permitted Failed to determine whether /sys/fs/cgroup is a mount point: Operation not permitted Failed to determine whether /sys/fs/cgroup/systemd is a mount point: Operation not permitted [!!!!!!] Failed to mount API filesystems, freezing. Freezing execution. Expected results: No error, systemd runs correctly. Additional info: This is a regression against Fedora 25 with docker-1.12.6-6.gitae7d637.fc25.x86_64 where systemd in container runs without error.
There are no AVC denials and the result is the same in permissive as well.
On rawhide, docker-1.13.1-9.git14cc629.fc27.x86_64 has the same problem.
This may be seccomp, could you try running with: docker run --security-opt seccomp:unconfined ...
(In reply to Antonio Murdaca from comment #3) > This may be seccomp, could you try running with: > > docker run --security-opt seccomp:unconfined ... That helps, at least on rawhide. Which component should this be tracked then?
It's a docker packaging issue. Lokesh, we should be shipping /etc/docker/seccomp.json as we did for RHEL some time ago. We should do it for both F26 and rawhide.
The issue is we need to allow name_to_handle_at in the custom seccomp profile in order to run systemd in a container.
Standa, per https://github.com/systemd/systemd/pull/6876#issuecomment-331161854 the workaround that we have in automation (and that potentially might be cause for https://bugzilla.redhat.com/show_bug.cgi?id=1492081) might not be needed because latest systemd fixed things. Could you please try without seccomp:unconfined?
Also, testing on RHEL 7.4 on the host (where the docker version < 1.13) could give use some clues ...
With docker-1.13.1-22.gitb5e3294.fc26.x86_64 and latest registry.fedoraproject.org/fedora:25 and registry.fedoraproject.org/fedora:26, the systemd runs without seccomp:unconfined.
Tested registry.fedoraproject.org/fedora:26 with docker-1.12.6-55.gitc4618fb.el7.x86_64 as well, works.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This issue seems to have been fixed some time ago. Could we get the proper Fixed In Version value and CURRENTRELEASE resolution?