I don't really understand the bug task on bind9 packaging here. If you
install the bind9 package, then surely you expect it to listen on IPv6
ports by default? If you don't want this, then presumably you need to
reconfigure bind9?
Setting the bind9 package task Incomplete because as far as I can
Actually I was thinking this was bug 1240757.
@zukoff-f: your comment #25 would be more appropriate there. That's
where we should discuss how to have bind9, dnsmasq, and lxc cooperate.
This bug seems to have evidence from several different causes.
yoniyo0's was a bad lxc-usernet file. I'm not
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Importance: High => Low
** Changed in: lxc (Ubuntu)
Status: Expired => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
bind9 and dnsmasq try to listen the same port on ipv6 (lxcbr0)
lxcbr0Link encap:Ethernet HWaddr xxx
inet addr:10.0.3.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::dc81:d8ff:feea:14b0/64 Scope:Link
tcp6 0 0 fe80::dc81:d8ff:feea:53 :::*
LISTEN
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Finally, on my host I get:
root@srv-Ub1404:~# ps -ef | grep dnsmasq
lxc-dns+ 11309 1 0 Jan15 ?00:00:00 dnsmasq -u lxc-dnsmasq
--strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file=
--listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254
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
Thanks for the update. So I'm still really curious how that defaults
file got so confused in the first place... It also may have something
to do with why you're still having trouble..
If dnsmasq is still badly installed then that would explain your
remaining issue.
What does:
sudo netstat -nr
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`
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
Ok, so we're now at a different bug. Could you please again show what
sudo brctl show
ifconfig -a
show and the container configuratio nfile? You're starting the container
as root? (If not, please show your /etc/lxc/lxc-usernet file contents)
--
You received this bug notification because you
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
Perhaps the already in use message being printed is a bug in the error
reporting on not finding the dnsmasq.conf file?
Please comment out that line in /etc/default/lxc-net, and let us know
whether that helps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
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
note i don't think this is a dup of bug 1240757 as you had original
speculated, because you do not seem to have any bind9 or dnsmasq
listening on 10.0.3.1.
Please attach your /etc/default/lxc-net file. Your lxc-net.log file
showed an error opening /etc/lxc/dnsmasq.conf, but the line which would
Hi, thanks for re-opening this bug.
Could you please show the results of:
ifconfig -a
brctl show
ps -ef
on the host?
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** 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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** 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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** 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
Touch seeded packages, 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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1367495
Title:
Bridge still not created if bind9 is on
Status
That all looks fine. Could you please try
sudo start lxc-net
and show any console output as well as attach /var/log/upstart/lxc-
net.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Thanks - these results don't quite make sense. What do the following
show:
sudo netstat -nr
sudo netstat -lnp | grep 10.0
traceroute 10.0.3.1
dpkg -l | grep dnsmasq
dpkg -l | grep lxc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
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
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Thanks for reporting this bug. I'm not sure it's actually a dup of
1240757, because the syslog seems to indicate that dnsmasq is offering
addresses over lxcbr0.
Could you do 'lxc-start -n container0 -l trace -o debug.out' and attach
debug.out here?
** Changed in: lxc (Ubuntu)
Status: New
28 matches
Mail list logo
