apparmor should quietly return success in a container
Bug #978297 reported by
Serge Hallyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apparmor (Ubuntu) |
Fix Released
|
High
|
Serge Hallyn | ||
Precise |
Fix Released
|
High
|
Serge Hallyn | ||
upstart (Ubuntu) |
Fix Released
|
High
|
Serge Hallyn | ||
Precise |
Fix Released
|
High
|
Serge Hallyn |
Bug Description
In precise, containers are not allowed to load profiles. This will be allowed later, but for now apparmor should not prevent things from starting in a container because of failures to load or transition to profiles.
1. /etc/init.
2. /lib/init/
Since the container is already locked into a (customizable) container profile, this is ok.
(Note that admins can have containers running unconfined and with all
capabilities, but that is a special case.)
THis is needed for bug 978147.
Related branches
Changed in apparmor (Ubuntu): | |
status: | New → In Progress |
Changed in upstart (Ubuntu): | |
status: | New → In Progress |
Changed in apparmor (Ubuntu): | |
importance: | Undecided → High |
Changed in upstart (Ubuntu): | |
importance: | Undecided → High |
Changed in apparmor (Ubuntu): | |
assignee: | nobody → Serge Hallyn (serge-hallyn) |
Changed in upstart (Ubuntu): | |
assignee: | nobody → Serge Hallyn (serge-hallyn) |
tags: | added: rls-mgr-p-tracking |
tags: | added: patch |
To post a comment you must log in.
Here is Serge's patch.