@Rahul, I still think it's a race where LXD creates the bridge `lxdbr0`,
assign it an IP, MAAS' bind9 starts listening on the new IP on port 53,
LXD starts up a dnsmasq that fails to bind port 53 on the new IP/NIC.
As mentioned in comment number 4, MAAS' bind9 could probably be
configured to not bind every new interface it discovers.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1995194/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
