Description of problem: Running docker run -ti --name systemd --rm registry.fedoraproject.org/fedora:28 /usr/sbin/init results in Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory Failed to set up the root directory for shared mount propagation: Operation not permitted Version-Release number of selected component (if applicable): docker-1.13.1-59.gitaf6b32b.fc28.x86_64 container-selinux-2.65-1.gitbf5b26b.fc28.noarch oci-systemd-hook-0.1.17-1.git87fb61e.fc28.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. Run docker run -i --name systemd --rm registry.fedoraproject.org/fedora:28 /usr/sbin/init 2. See it say Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory 3. In another terminal run docker exec systemd journalctl, see it print out some entries 4. In another terminal run docker rm -f systemd 5. Now repeat with -t option added to the docker run command: docker run -ti --name systemd --rm registry.fedoraproject.org/fedora:28 /usr/sbin/init Actual results: Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory Failed to set up the root directory for shared mount propagation: Operation not permitted and docker exec systemd journalctl prints -- No entries -- No journal files were found. Expected results: The output with -ti should be the same as with -i. Additional info:
I managed to hit Enter too soon and created duplicate bugzillas. *** This bug has been marked as a duplicate of bug 1615082 ***