Well, it does help `lxc-net` create the bridge (shown on `brctl show` and
`ifconfig`), but apparently not to configure it appropriately. `lxc-net` is
still not listed when I run `service --status-all`, and attempting to start a
container returns:
server@srv-Ub1404:~$ lxc-start -n u1
Quota reached
lxc_container: failed to create the configured network
lxc_container: failed to spawn 'u1'
lxc_container: The container failed to start.
lxc_container: Additional information can be obtained by setting the
--logfile and --logpriority options.
The log for `lxc-net` (attached) still contains the same errors (odd;
why would it look for `dnsmasq.conf`?), but now it also contains
something about a bad IPTABLES rule (I'm not sure how to check which
one).
** Attachment added: "lxc-net.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4296741/+files/lxc-net.log
--
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
