Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 420655 - sys-apps/openrc-0.9.9.3 && lxc: Fail to start network devices for containers in net.*
Summary: sys-apps/openrc-0.9.9.3 && lxc: Fail to start network devices for containers ...
Status: RESOLVED DUPLICATE of bug 410701
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: OpenRC (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: OpenRC Team
URL:
Whiteboard: openrc:oldnet
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-11 08:56 UTC by Guido Jäkel
Modified: 2013-04-25 23:08 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guido Jäkel 2012-06-11 08:56:40 UTC
When starting a LXC container, wiht openrc-0.9.9.3 the local init fails on network setup with the message

 * Bringing up interface lo
 *   ERROR: interface lo does not exist
 *   Ensure that you have loaded the correct kernel module for your hardware
 * ERROR: net.lo failed to start



To my analysis this happens because now  /lib/rc/net/ifconfig.sh  uses the sysfs to check if an interface is present. In previous versions (at least 0.9.8.4) the procfs was used

_exists()
{
-        grep -Eq "^[[:space:]]*${IFACE}:" /proc/net/dev
+        [ -e /sys/class/net/"$IFACE" ]
}


But inside a container, the  /etc/init.d/sysfs  isn't triggered to start (, on the host this will be done by a 'need' in udev).

I think with the change in code above, one have to add a sysfs to the needs in  /etc/init.d/net.lo at line 21

For me, this solves the issue: The sysfs script now is started just before the start of the loopback interface.
Comment 1 William Hubbs gentoo-dev 2012-06-11 21:04:49 UTC

*** This bug has been marked as a duplicate of bug 410701 ***
Comment 2 Guido Jäkel 2012-06-12 06:39:25 UTC
Confirmed. 

Thank you, William.