[Bug 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)

[Serge Hallyn]

It turns out the original problem never went away.  The container never
gets a net-device-up event for lo, even in precise.  You can verify this
trivially with two upstart jobs, /etc/init/lxc{lo,eth}.conf:

==== lxclo.conf ====
description "detect net-device-up IFACE=lo"
start on net-device-up IFACE=lo
==== lxceth.conf ===
description "detect net-device-up IFACE=eth0"
start on net-device-up IFACE=eth0
====================

Start the container and check 'status lxclo' and 'status lxceth'.

The reason this happens is clear in /etc/network/if-up.d/upstart.  The reason
this stopped mattering is that rc-sysinit.conf switched from being

start on filesystem and net-device-up IFACE=lo

to being

start on (filesystem and static-network-up) or failsafe-boot

Where static-network-up does not require lo to come up.

-- 
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/924337

Title:
  lxc on precise is not working with lucid containers (container does
  not reach runlevel 2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+subscriptions