unconfined containers are not starting
Bug #987371 reported by
Serge Hallyn
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apparmor (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Quantal |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
lxc (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Quantal |
Invalid
|
Critical
|
Unassigned |
Bug Description
lxc-create -t ubuntu -n p1
lxc-start -n p1
That works.
Uncomment the 'lxc.aa_profile = unconfined' in /var/lib/
lxc-start -n p1
does not work.
The relevant code in src/lxc/start.c does:
if (aa_change_
}
By default (when it works), hander-
lxc-container-
Changed in linux (Ubuntu Precise): | |
status: | New → Fix Committed |
Changed in lxc (Ubuntu Precise): | |
status: | New → Invalid |
Changed in apparmor (Ubuntu Precise): | |
status: | New → Invalid |
To post a comment you must log in.
Sorry, the relevant error message is:
lxc-start: No such file or directory - failed to change apparmor profile to unconfined