Bug 1312665
| Summary: | selinux daemon flag breaks docker user namespaces | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Antonio Murdaca <amurdaca> |
| Component: | docker | Assignee: | Matthew Heon <mheon> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | adimania, admiller, amurdaca, dwalsh, ichavero, jcajka, jchaloup, jhonce, lsm5, marianne, miminar, vbatts |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 11:02:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Antonio Murdaca
2016-02-28 16:00:33 UTC
This bug is also present in the current 1.10.x version we'd like to ship to f23 which is in updates-testing What AVC's are you seeing. ausearch -m avc -ts recent $ ausearch -m avc -ts recent
----
time->Mon Feb 29 10:02:39 2016
type=AVC msg=audit(1456758159.888:355): avc: denied { getattr } for pid=3002 comm="ls" path="/dev/fuse" dev="devtmpfs" ino=13993 scontext=system_u:system_r:svirt_lxc_net_t:s0:c280,c1010 tcontext=system_u:object_r:fuse_device_t:s0 tclass=chr_file permissive=0
----
time->Mon Feb 29 10:04:54 2016
type=AVC msg=audit(1456758294.444:429): avc: denied { create } for pid=3417 comm="systemd-user-se" name=".#nologinPQgyBA" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_run_t:s0 tclass=file permissive=0
----
time->Mon Feb 29 10:05:13 2016
type=AVC msg=audit(1456758313.361:264): avc: denied { create } for pid=1016 comm="systemd-user-se" name=".#nologin8D85lp" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:systemd_logind_var_run_t:s0 tclass=file permissive=0
-----
Are those related? I got those after I did docker run -ti busybox sh
Also:
docker run -ti -v /dev/mqueue:/dev/mqueue busybox sh seems to be working
also bind-mounting dev mqueue from the host seems to have the correct ownership: drwxrwxrwt 2 65534 65534 40 Feb 29 15:05 mqueue I'm not sure this is right setenforce 0 Does it only give you the fusefs error? Does user namespace use /dev/fuse? This seems to be a new file system in the os. We can add the ability for svirt_lxc_net_t to use them alright setenforce 0 doesn't change the situation here, the only thing which makes this work is removing --selinux-enabled from the daemon OPTION= in /etc/sysconfig/docker - not sure what's happening, I'll try to debug it WRT /dev/fuse - yes it seems a new fs in rawhide, we can add svirt_lxc_net_t so ppl can use it This dmesg message may be helpful though: [ 75.816990] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) That is actually hanlded currently, but not for /dev/fuse. Is /dev/fuse something new for docker-1.11? (In reply to Daniel Walsh from comment #8) > That is actually hanlded currently, but not for /dev/fuse. Is /dev/fuse > something new for docker-1.11? I don't think so, I do have to check but I doubt. still, why the selinux-flag is causing this? I spin up another rawhide vm and ausearch output is empty. If it is breaking, add semodule -DB setenforce 0 Run docker tests setenforce 1 semdodule -B And attach the avcs. Really only looking at svirt_lxc_net_t ones. This has been also reported upstream https://github.com/docker/docker/issues/20798 will be fixed in docker 1.11 as per upstream issue https://github.com/docker/docker/issues/20798 This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |