No IP address is assigned inside the container when starting

[Christopher Townsend]

Recently, no IP address is being assigned inside the Unity 8 container when it starts.

Looking at /var/log/syslog in the container indicates that the DHCP service is not running when the container starts. Need to investigate why this is so.

Issuing 'sudo lxc-attach -n unity8-lxc -- restart newtork-manager' will get an IP address and I can see in the log where the DHCP is called.

[Christopher Townsend (townsend)]

I had an older ubuntu-desktop-next ISO and using the same exact config, that ISO will have an IP address after starting the container. Based on this, there is something in the ISO that is not playing nice with container. Adding debugging to NetworkManager does not show any errors. It just looks like it doesn't try to obtain an IPv4 address.

I would rather find the cause of this, but I may end up having to add some workaround to force the container to get an IP address.

[Christopher Townsend (townsend)]

I downgraded the version of network-manager in the container to 0.9.10.0-4ubuntu1 and the issue still occurs. I then downgraded to 0.9.8.8-0ubuntu34 (which required me to downgrade ppp to 2.4.5-5.1ubuntu5) and now the container obtains an IP address.

I strongly suspect a change in network-manager now causes this (and not ppp), but that was such a large update, it's hard to tell what it could be.

I'm really leaning towards adding a workaround to get the IP address now based on the issue being in network-manager.

[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