[Lxc-users] unable to add empty network (type=empty)

Daniel Lezcano daniel.lezcano at free.fr
Thu Feb 11 21:10:15 UTC 2010

Tony Risinger wrote:
> in the vps-lxc tool ive written:
> http://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg00148.html
> the default profile generates a domain config file that looks like this:
> # generated by mkdom
> # Thu Feb 11 14:50:34 CST 2010
> lxc.rootfs=/vps/var/lib/vps-lxc/dom/test1/rootfs
> lxc.mount=/vps/var/lib/vps-lxc/dom/test1/fstab
> lxc.utsname=test1
> lxc.tty=2
> lxc.pts=1024
> lxc.network.type=empty
> however when i try to start it with my tool, (i just want to
> demonstrate how mine works, i want to spread it! :-) i get:
> ph1 ~ # vps-lxc start test1
> info: starting domain test1...
> FATAL exception encountered... stacktrace:
>    start(vps_cmd_main):92 info: starting domain test1...
>    start(vps_cmd_main):102 fatal: domain test1 started, but is not RUNNING
> when i try to run it manually i get:
> ph1 ~ # lxc-start -n test1
> lxc-start: failed to move '(null)' to the container
> lxc-start: failed to create the configured network
> lxc-start: failed to spawn '/sbin/init'
> why is this?  am i missing something to get lxc-* tools to just create
> a new, empty network stack?  the idea was to have the default
> distribution profile create domains with an empty network, since i
> don't know anything about the host environment.  if i make a "veth"
> network instead, it starts/runs fine.

You find a bug :)
It's regression regarding the previous version.

Will fix it.

   -- Daniel

ps: vps-lxc looks nice, you did an impressive work.

ps2 : I finally implemented the shutdown/reboot from a container using 
the utmp watching method but it is embedded in lxc now. That works 
pretty well for me. It is not yet committed.

More information about the lxc-users mailing list