** Description changed:
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.
+ ======================================
** Changed in: lxc (Ubuntu Quantal)
Status: New => Triaged
** Changed in: lxc (Ubuntu Quantal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1070914
Title:
lucid containers don't start on quantal hosts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1070914/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
