Error parsing lxc-start apparmor profile
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Unassigned |
Bug Description
=======
SRU Justification:
1. Impact: cannot start containers with read-only proc
2. Development fix: remove \n from /proc/pid/
3. Stable fix: cherrypick development fix.
4. Test case:
a. lxc-create -t ubuntu -n u1
b. sudo sed -i '/proc/
c. echo "lxc.aa_profile = unconfined" | sudo tee -a /var/lib/
d. apparmor_parser -R /etc/apparmor.
e. sudo lxc-start -n u1
5. Regression potential: none, this only makes us ignore the \n at end of /proc/pid/
=======
The lxc-start package reads its apparmor profile from /proc/$
Ubuntu release:
Description: Ubuntu 13.04
Release: 13.04
Package being used:
lxc:
Installed: 0.9.0-0ubuntu3.5
Candidate: 0.9.0-0ubuntu3.5
Version table:
*** 0.9.0-0ubuntu3.5 0
500 http://
100 /var/lib/
0.
500 ftp://repos.
0.9.0-0ubuntu3 0
500 ftp://repos.
What is expected to happen:
A container with a read-only /proc filesystem should start successfully.
What happened instead:
lxc-start fails with "Read-only file system - failed to change apparmor profile to unconfined"
Related branches
Changed in lxc (Ubuntu): | |
importance: | Undecided → Medium |
Status changed to 'Confirmed' because the bug affects multiple users.