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 has a feature that spawns listeners on newly created interfaces, so maybe MAAS could turn that feature off to play more nicely with other listeners? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
