Aha! It was an unprivileged container (I used to get the same error
messages with privileged and unprivileged containers), and it turns out
in one of my purge - install cycles I forgot to add "$USER veth lxcbr0
2" to `/etc/lxc/lxc-usernet`. I did that (it's now the only line there
after the first commented title line), and now I can start the
container! (I rechecked: privileged containers also start.)
In both cases, however, the network is unreachable from within the
container, as evident by the response `connect: Network is unreachable`
to my pinging my host and/or router. I guess that's not surprising
considerng that `lxc-net` still returns all of these error messages.
However, that's truly a separate issue now, so it's worth summing up
that the uncommented line in `/etc/default/lxc-net` (which was installed
that way, for some reason) was the cause of this bug on my machine. I'm
not sure what to do regarding the new issue (I haven't googled about it
yet), so I'll include what you've asked for just in case you spot an
easy fix. (BTW, I don't know if this belongs on this medium, but you
have my sincere thanks for your help. It was invaluable.)
server@srv-Ub1404:~$ sudo brctl show
bridge name bridge id STP enabled interfaces
lxcbr0 8000.fedfa607a667 no vethA4H3U6
server@srv-Ub1404:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1b:fc:8e:95:ba
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::21b:fcff:fe8e:95ba/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7417201 errors:0 dropped:0 overruns:0 frame:0
TX packets:1758168 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:10608089410 (10.6 GB) TX bytes:1646751692 (1.6 GB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2867 (2.8 KB) TX bytes:2867 (2.8 KB)
lxcbr0 Link encap:Ethernet HWaddr fe:df:a6:07:a6:67
inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0
inet6 addr: fe80::98d6:4cff:fe27:2ea2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19844 (19.8 KB) TX bytes:7380 (7.3 KB)
vethA4H3U6 Link encap:Ethernet HWaddr fe:df:a6:07:a6:67
inet6 addr: fe80::fcdf:a6ff:fe07:a667/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13986 (13.9 KB) TX bytes:1706 (1.7 KB)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Bridge still not created if bind9 is on
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
