Unity 8 container does not start when starting a session in Vivid

[Christopher Townsend]

When choosing to start the Unity8 LXC session in LightDM, you will see LightDM just hang.

This is caused by a recent change in LXC which causes the Unity 8 container to not start. I filed bug #1417909 in the LXC package, but was told that I'm missing a config entry:

lxc.mount.auto = sys

This is new behavior that will be worked around by adding this config entry in the unity8-lxc-setup script.

[Launchpad Janitor (janitor)]

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 <email address hidden> Thu, 05 Mar 2015 14:48:22 +0000