Package: lxc
Version: 0.7.5-12
Severity: grave
Justification: renders package unusable
Dear Maintainer,
It seems that LXC uses invalid veth names when launching a new
container.
If you create two container using virtual Ethernet interfaces, the first
one
will load fine but with the second one, you will have the following
error:
# lxc-start -n <container> -f /srv/lxc/<container>/config
lxc-start: failed to create veth--veth854Hig : File exists
lxc-start: failed to create netdev
lxc-start: failed to create the network
lxc-start: failed to spawn '<container>'
lxc-start: No such file or directory - failed to remove cgroup
'/cgroup/<container>'
It looks like LXC is trying to create an interface named
`veth--veth854Hig' but
this name is invalid due to the two `-'.
A look at ifconfig can confirm that:
# ifconfig -a
veth- Link encap:Ethernet HWaddr be:86:2f:8a:fe:3b
inet6 addr: fe80::bc86:2fff:fe8a:fe3b/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:5291 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2008 (1.9 KiB) TX bytes:537310 (524.7 KiB)
So when we launch a second container, it is conflicting with the already
created
`veth-' interface.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-21
ii libcap2 1:2.22-1
Versions of packages lxc recommends:
ii debootstrap 1.0.38
ii libcap2-bin 1:2.22-1
Versions of packages lxc suggests:
pn lxctl <none>
-- debconf information:
lxc/shutdown: stop
lxc/directory: /var/lib/lxc
lxc/title:
lxc/auto: true
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
