This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu44
---
lxc (0.8.0~rc1-4ubuntu44) raring; urgency=low
[ Scott Moser ]
* 0225-ubuntu-cloud-numeric-owner: use --numeric-owner when extracting root
filesystems with tar (LP: #1066084)
[ Serge Hallyn ]
* Remove 0224-ubu
Patch 0224-ubuntu-templates-devtmpfs still needs to be removed from the
raring package.
** Changed in: lxc (Ubuntu Raring)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc i
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu38
---
lxc (0.8.0~rc1-4ubuntu38) quantal-proposed; urgency=low
[ Scott Moser ]
* 0225-ubuntu-cloud-numeric-owner: use --numeric-owner when extracting root
filesystems with tar (LP: #1066084)
[ Serge Hallyn ]
* Remov
** Branch linked: lp:ubuntu/quantal-proposed/lxc
--
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 abo
Tested the fix with all supported Ubuntu relesaes. Works fine with the ubuntu
template.
For the ubuntu-cloud template, quantal works but precise is still lacking /dev
entries, though as mentioned, it'll be fixed with the next build so it's all
good on lxc's side.
** Tags removed: verification-n
Flagging for security as the version currently in quantal basically lets
a container do pretty big damage to the host and any other container by
removing or messing with /dev entries.
** Information type changed from Public to Public Security
--
You received this bug notification because you are
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.
** 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
** Also affects: lxc (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Raring)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bu
