Oh I just meant for kernel-space. So if a container is creating lo,
it will create a device named lo, but the sysfs file will be called
lo_1 or something.
Yes, the above would require that the container either not mount
sysfs, ignore sysfs, or tweak sysfs using
mount -t tmpfs none /sys/class/net
mount --bind /sys/devices/virtual/net/lo_1 /sys/class/net/lo
or using fuse.
I'd definately prefer the sysfs tagging approach. But I'd prefer
the above over never being able to use network namespaces on a
standard distro (with sysfs enabled).
-serge
--
