https://bind9.readthedocs.io/en/v9.18.27/reference.html#namedconf-
statement-automatic-interface-scan is the default enabled feature that
causes bind9 to start the conflicting listener, or at least I think it
is.
I believe this is more a bug with how MAAS configures bind9 than
something LXD could
If I'm reading the issue properly, that 10.37.129.1 address would be
from the newly created `lxdbr0` bridge where LXD wants to setup a
dnsmasq listener.
Now presumably that fails because something in MAAS (bind9?) raced with
it and started a listener on it before dnsmasq got a chance.
IIRC, bind9
You can also just:
sudo snap stop maas
Then init lxd
No need to remove the maas snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1995194
Title:
lxd init fails with 'Address already in use'
To
