On 05/05/2016 02:32 AM, Naina Emmanuel
wrote:
The HOSTS SELinux policy affects the container. Inside of the containers, the system thinks that SELinux is disabled. We don't allow you to run two different SELinux policies with the same kernel. You would need kvm/virtualization for this and to have a separate VM from the host. If you are running unconfined_t then you are running on a targeted host, What the configuration of content inside of the container does not matter. See above. Docker should be running as docker_t, if you have docker-selinux package installed and everything labeled properly. I have never heard of these, The docker-selinux policy ships with the docker.te, it also uses types defined in the virt.te files. MLS Policy and targeted are shared. MLS Should be able to work with docker-selinux, with a few tweaks to make sure that docker_t runs ranged. May need some mls overrides. You might also need to add virt.pp if that is not in the default mls package. I would suggest that you setup the host to run in MLS mode and then modify docker-selinux package to run in an MLS environment. docker will pick out random MCS Labels for running containers, so you would need to override this behaviour if you want a container to run at a particular level. Something like docker run -ti --security-opt label=level:s15:c1,c2 rhel7 /bin/sh
|
_______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.