[Lxc-users] eth0 not coming online in LXC environment

[David Parks]

Oops, forgot that important detail, running Ubuntu 12.10 as the host OS
installed off media, and I have 12.10 running in these LXC containers built
from the Ubuntu cloud distros (12.10 64bit).  

 

 

From: Fajar A. Nugraha [mailto:list at fajar.net] 
Sent: Friday, April 05, 2013 4:09 PM
To: David Parks
Cc: LXC
Subject: Re: [Lxc-users] eth0 not coming online in LXC environment

 

On Fri, Apr 5, 2013 at 10:33 AM, David Parks <davidparks21 at yahoo.com> wrote:

I've got an environment set up now where the host OS has a static IP
directly connected to the LAN. I'm bridging the containers to have their own
static LAN IP as well.

 

When I start my container eth0 is *not* configured. If I manually add
`eth0=eth0` in /run/network/ifstate and `service restart networking`, it
gets configured properly.

 

 

After looking at dmesg output I noticed that there are (unexpected)
references to em1, which is the host's physical NIC.

 

The bridging all works, networking is fine, it's just when I start the
container, rebooting reproduces the problem, then manually updating ifstate
and rebooting resolves it.

 

I'm not sure how to configure it so it configure eth0 on reboot as I would
expect.

 

Well, a description on which distro/version you're running as host and
container would be nice.

 

Short version is if you use Ubuntu (preferably quantal/raring for newer lxc
version, but precise is also fine), then it will just work. If you use some
other combination (e.g. Centos for container), then be prepared for hickups.

 

I had problems with Centos container, and the "fix" was to force-clean
/var/run and /var/lock/subsys on container startup:
https://github.com/fajarnugraha/lxc/blob/centos-template/templates/lxc-cento
s.in#L90

 

-- 

Fajar

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20130405/e2cbdeaf/attachment.html>