Okay. FYI I went ahead and defined my own bridge to let containers
communicate directly with my router's dhcp server, but I've created and
started a new privileged container `pr1` and made sure it uses `lxcbr0`
and not my `br0`. Still, it's possible I'll have to tell `lxcbr0` to
plug into `br0`
Not by design, no. Any of that, really, since I wouldn't have known
where to go to make these alterations if I wanted to (well, now that you
pointed that out, I should be able to reverse-engineer it and see if it
at least assigns IP addresses to containers automatically that way).
It's a pretty
Well, I can't attest to Dan Kegel's setting, but this is my copy of
`/etc/default/lxc-net`. Indeed, that line isn't commented out, and I
don't have a `dnsmasq.conf` in `/etc/lxc`.
** Attachment added: lxc-net
This is odd. On advice from Flockport community I attempted to manually
configure the bridge (its basic elements, at least) by entering
sudo brctl addbr lxcbr0
sudo ifconfig lxcbr0 10.0.3.1 netmask 255.255.255.0 up
This went just fine, with `ifconfig` reporting (beyond those interfaces
Wait, 'lxc-net' does show as `running` when I run `initctl list`. I
guess that's what I get for not checking if the manuals I've been using
are 100% compatible with my distro.
Regardless, it still gives those errors, and starting containers fails
with that seemingly network-related message.
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
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
** Attachment added: ps.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294749/+files/ps.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
** Attachment added: brctl.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294748/+files/brctl.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1367495
** Attachment added: ifconfig.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+attachment/4294747/+files/ifconfig.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Bridge still not created if bind9 is on
To manage
Certainly. The service was already running, so I stopped and restarted
it for good measure.
root@srv-Ub1404:~# start lxc-net
start: Job is already running: lxc-net
root@srv-Ub1404:~# stop lxc-net
lxc-net stop/waiting
root@srv-Ub1404:~# start lxc-net
lxc-net start/running
`sudo netstat -nr` returns:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
0.0.0.0 my-net.1 0.0.0.0 UG0 0 0
eth0
my-net.0 0.0.0.0 255.255.255.0 U 0 0 0
13 matches
Mail list logo
