Fedora Account System
Red Hat Associate
Red Hat Customer
I'm using Docker for random rel-eng stuff, where some data is stored on the host. For other reasons, most of my containers are --privileged, but there's one that doesn't need to be. However, if I want to do bind mounts, I need to relabel the files with svirt_sandbox_file_t, which is kind of annoying in this case. What might be nice is if we had a --read-system or so flag which would run the app in a new domain variant like svirt_lxc_net_readsys_t ? I think it's having to copy the data for *reading* that's kind of annoying. I expect to have to do it for writes.
We could add a new type that would be allowed to look at all types. Then you could do something like docker run -ti --security-opt label:type:svirt_lxc_read_readsys_t ... I talked about this in my blog on opensource.com http://opensource.com/business/15/3/docker-security-tuning It would be simple enough to do, and might be a good example.
policy_module(mycontainer, 1.0) virt_sandbox_domain_template(container_read_all) files_read_non_auth_files(container_read_all_t) files_list_non_security(container_read_all_t) allow container_read_all_t self:capability *;
# docker run --security-opt label:type:container_read_host_t -ti --rm -v /:/host fedora /bin/sh
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Miroslav this might be another use case for the redesigned policy.
Yeap. I created https://github.com/mgrepl/seatomic/wiki/Design#scope where we could collect all these bugs.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.