This bug was fixed in the package unity8-lxc -
1.0.3+15.04.20150305.1-0ubuntu1
---------------
unity8-lxc (1.0.3+15.04.20150305.1-0ubuntu1) vivid; urgency=medium
[ Chris Townsend ]
* Bump version to 1.0.3.
* Add an lxc-wait after lxc-start to make sure the container is
actually running before proceeding to the lxc-attach. Also, have to
add an additional half second sleep to account for an lxc race where
lxc-wait reports the container is running when in reality, it may
not be. (LP: #1425663)
* Add config entry to automount sys to work around a new LXC behavior
in 15.04 and later. (LP: #1420468)
* Disable the new autodev feature in LXC as it only creates a minimal
/dev in the container and we need a full /dev. (LP: #1425684)
* Do not include the default lxc network config as using the
'flags=up' from it confuses NetworkManager inside the container.
(LP: #1427743)
* Fix issue where zsync doesn't seem to handle cross linking across
filesystems and also detect if the ISO did not download and throw an
error. (LP: #1418671)
[ CI Train Bot ]
* New rebuild forced.
-- CI Train Bot <ci-train-...@canonical.com> Thu, 05 Mar 2015 14:48:22 +0000
** Changed in: unity8-lxc (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420468
Title:
Unity 8 container does not start when starting a session in Vivid
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-preview-lxc/+bug/1420468/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
