Red Hat Bugzilla – Bug 1014707
selinux policy to constrain docker containers
Last modified: 2015-06-29 08:31:25 EDT
Docker is an exciting new interface to containers on Fedora, but does not offer any particularly strong security. Having a great SELinux policy which keeps the container isolated would be very helpful to our users and compelling for people choosing an underlying platform for Docker.
I have no idea exactly what this would look like, but I know people who do. :)
Ideally, we would have either something which works with both libvirt-lxc or the sourceforge lxc fallback. Or, we should (as a separate issue) warn when using the fallback if that's not possible.
IIUC it does not currently use user namespaces, so it probably has very weak security indeed. Enabling user namespaces would help (but uid 0 would have to be mapped through to make things look sane from outside).
Selinux is probably a good idea, too. I wonder if it's possible to make selinux work right from inside the containers, too.
Working on it, along with integration into libvirt. Hopefully will work with docker .85.
I would like to see usernamespace turned on also, Security in layers.
Getting SELinux to work within the containers is more of a long range project. Meaning we can prevent containers from interfering with the host machine or other containers using SELinux. But using SELinux to isolate two different processes within a container is difficult. For example if you have apache and mysql running within the same container, SELinux will run all processes with the same label, giving them the same rights.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Thank you for reporting this bug and we are sorry it could not be fixed.