The remaining part of the fix appears to be to remove lxcguest
manually from your existing lxc guest.
--
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/892892
Title:
mountall upgrade
The new upstart conflicts with lxcguest, so lxcguest is automatically
removed from the Precise containers.
--
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/892892
Title:
mountall upgrade
lxcguest has been removed.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
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/892892
Title:
mountall upgrade fails to
As soon as a few changes hit upstart, we will get rid of lxcguest, which
will close this bug.
--
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/892892
Title:
mountall upgrade fails to
Thanks for reporting this bug.
The reason for this is that lxcguest bind-mounts a custom fstab over
/lib/init/fstab when a container is booted. For the precise cycle, we
intend to fix mountall so that we'll no longer need that hack. Once
that's done, mountall upgrades will be able to proceed.
