On Thu, Oct 11, 2012 at 12:16 PM, Serge Hallyn
serge.hal...@canonical.com wrote:
Thanks, Dan. I've reproduced it and commented in the bug. It's not
really a bug in lxc. I at least when the veth is destroyed a uevent
should be sent saying net-device-removed. Still digging/thinking.
Now I
On 10/11/2012 03:18 PM, Dan Kegel wrote:
On Thu, Oct 11, 2012 at 12:16 PM, Serge Hallyn
serge.hal...@canonical.com wrote:
Thanks, Dan. I've reproduced it and commented in the bug. It's not
really a bug in lxc. I at least when the veth is destroyed a uevent
should be sent saying
Hi,
Dan Kegel (cc:d) found an interesting nuisance relating to upstart
and network interfaces with lxc containers. In particular, when you
start a container, two veths are created. A uevent for their creation
is sent, and so a 'network-interface' upstart job is created for each.
One of the
