Skip to content
This repository has been archived by the owner on Apr 19, 2019. It is now read-only.

Some containers are using unconfined apparmor profiles #19

Closed
mancdaz opened this issue Sep 1, 2014 · 0 comments
Closed

Some containers are using unconfined apparmor profiles #19

mancdaz opened this issue Sep 1, 2014 · 0 comments

Comments

@mancdaz
Copy link
Contributor

mancdaz commented Sep 1, 2014

Issue by Apsu
Monday Jul 28, 2014 at 16:18 GMT
Originally opened as https://github.com/rcbops/ansible-lxc-rpc-orig/issues/239


Some containers, such as neutron-agents, nova-compute and cinder-volumes are disabling apparmor by setting their profile to "unconfined". This is primarily due to us failing to figure out the right way to provide access to all the host resources and capabilities ( https://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.2/capfaq-0.2.txt ) required to do the needful.

We should figure out how to use apparmor correctly so we can at least make a passable attempt at locking these containers down as much as possible, in line with the rest of the cluster containers.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants