Containers not getting IPV4 - no dnsmasq?

LXD
1

Hi,

I just upgraded my Ubuntu server from 18.04 to 20.04. This didn’t went smooth due to problems with netboot and kernel not supporting ZFS…

At the end, I had to re-connect lxd to :lxd-support, :network :network-bind and :system-observe manually, and lxd started. My precious containers are now running.

BUT… they don’t get any IP (neither V4 nor V6). It seems, that dnsmasq is not running…

$ lsof -n -i :53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 1041 systemd-resolve 12u IPv4 21077 0t0 UDP 127.0.0.53:domain
systemd-r 1041 systemd-resolve 13u IPv4 21078 0t0 TCP 127.0.0.53:domain (LISTEN)
named 1075 bind 37u IPv4 25907 0t0 UDP 127.0.0.1:domain
named 1075 bind 38u IPv4 25908 0t0 UDP 127.0.0.1:domain
named 1075 bind 39u IPv4 25909 0t0 UDP 127.0.0.1:domain
named 1075 bind 40u IPv4 25910 0t0 UDP 127.0.0.1:domain
named 1075 bind [… bunch of named…]

$ lxc network show lxdbr0
config:
ipv4.address: 10.118.157.1/24
ipv4.nat: “true”
ipv6.address: fd42:7615:f675:2b5f::1/64
ipv6.nat: “true”
description: “”
name: lxdbr0
type: bridge
used_by:

  • /1.0/instances/[…all-my-containers…]
  • /1.0/profiles/default
    managed: true
    status: Created
    locations:
  • none

What should I do at this point ?
Thanks
Franck

2

Your bind9/named is likely listening on port 53 for all interfaces preventing LXD’s dnsmasq from starting up.

Either remove bind9 if you don’t use it or configure it to listen only on the specific interfaces/addresses that you need it on.

1 Like
3

Thanks Stéphane for taking the time to answer such newbie questions. You rock.