| Summary: | sys-apps/openrc-0.9.9.3 && lxc: Fail to start network devices for containers in net.* | ||
|---|---|---|---|
| Product: | Gentoo Hosted Projects | Reporter: | Guido Jäkel <G.Jaekel> |
| Component: | OpenRC | Assignee: | OpenRC Team <openrc> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | flameeyes, G.Jaekel |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | openrc:oldnet | ||
| Package list: | Runtime testing required: | --- | |
*** This bug has been marked as a duplicate of bug 410701 *** Confirmed. Thank you, William. |
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.