lucid containers don't start on quantal hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Serge Hallyn | ||
Quantal |
Fix Released
|
High
|
Unassigned | ||
Raring |
Fix Released
|
High
|
Serge Hallyn |
Bug Description
Because devtmpfs is now mounted in containers, and /dev/shm is a symlink in devtmpfs, lucid containers now fail to start.
=======
SRU Justification:
1. Impact: newly created lucid containers cannot be started, and changes in
the container's /dev are seen in the host's /dev.
2. Development fix: devtmpfs is removed from the container fstabs
3. Stable fix: same as development fix
4. Test case:
1. sudo lxc-create -t ubuntu -n l1 -- -F -r lucid
2. sudo lxc-start -n l1 -d
3. sudo lxc-ps -n l1
Only three tasks will show up in lxc-ps, because lxc-start will hang at
mountall when failing to mount /dev onto a symbolic link (/dev/shm).
5. Regression potential: This will require workarounds in the cloud images
(which recently stopped including a populated /dev, and will need to do so
again). That will be fixed by utlemming by Oct 25. It also regresses a bug
in grub updates in containers. This will need to be worked around by having
update-grub detect that it is in a container, and not fail due to non-existing
/dev/root in that case.
=======
Related branches
description: | updated |
Changed in lxc (Ubuntu Quantal): | |
status: | New → Triaged |
importance: | Undecided → High |
Hello Serge, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ lxc/0.8. 0~rc1-4ubuntu38 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!