Unable to start containers without proc entry in fstab
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
This bug affects all arkose containers.
Since the recent change to implement per-container apparmor profile, arkose stopped working, printing:
lxc-start: No such file or directory - failed to change apparmor profile to lxc-container-
Trying to reproduce this with a standard container, I tracked it down to the lack of /proc defined in LXC's fstab.
Arkose usually starts the container without giving lxc a fstab file, then after that mounts some file systems, I should change that anyway and will do so post-beta2 but the problem remains that it's currently impossible to start a container that doesn't use lxc's fstab to mount /proc.
On top of arkose container, this also breaks anyone using my recommended setup to boot VM images in a container per http://
Targeting to beta2 as it's currently breaking a software shipped by default on one of the images.