This bug was fixed in the package lxc - 0.7.5-0ubuntu8.2
---
lxc (0.7.5-0ubuntu8.2) oneiric-proposed; urgency=low
* debian/patches/0009-ubuntu-template-drop-resolvconf.patch:
Drop resolvconf from package list for oneiric containers. It appears
to stop containers from gettin
** Tags removed: verification-needed
** Tags added: verification-done
--
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/880030
Title:
oneiric container problem: missing /run/lock
To manag
tested and now is ok.
--
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/880030
Title:
oneiric container problem: missing /run/lock
To manage notifications about this bug go to:
https://bu
** Branch linked: lp:ubuntu/oneiric-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/880030
Title:
oneiric container problem: missing /run/lock
To manage notifications about
Hello xlyz, or anyone else affected,
Accepted lxc into oneiric-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** A
** Description changed:
host: oneiric with server minimal install + lxc + bridge_utils (bridge
manually set up)
guest: oneiric
every time the container is started /run/lock is missing.
I then create it manually, and next time is gone again.
+
+
This bug was fixed in the package lxc - 0.7.5-0ubuntu10
---
lxc (0.7.5-0ubuntu10) precise; urgency=low
* debian/patches/0009-ubuntu-template-drop-resolvconf.patch:
Drop resolvconf from package list for oneiric containers. It appears
to stop containers from getting a useful
quick fix to lxc-ubuntu while waiting lxcguest to be fixed (just in
case...)
chroot $rootfs apt-get install --force-yes -y lxcguest
+ # fix for oneiric /var/lock
+ if [ $release = "oneiric" ]; then
+ sudo sed -i '/touch \/var\/run\/utmp/ i\
+mkdir -p \/run
Thanks for reporting this bug.
This is another side effect stemming from the fact that the kernel
doesn't provide a good way to detect poweroff.vs.reboot in containers
yet. The workaround is for the container parent to watch the
container's /var/run/utmp. As a result of that, we can't let the
co
