maas should be able to configure what addresses its DNS server listens on
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
The MAAS snap currently cannot be used simultaneously with the multipass snap since MAAS wants to own DNS and it listens on 0.0.0.0 which means that it is listening to all addresses, including some addresses that are owned by the multipass snap's bridge it sets up.
When this happens, the multipass snap cannot startup:
Oct 01 08:55:26 multipassd[371104]: Using AppArmor support
Oct 01 08:55:26 multipassd[371104]: Starting dnsmasq
Oct 01 08:55:26 multipassd[371104]: Applied AppArmor policy: multipass.dnsmasq
Oct 01 08:55:26 multipassd[371104]: [371166] started: dnsmasq --keep-
Oct 01 08:55:26 multipassd[371104]:
Oct 01 08:55:26 multipassd[371104]: dnsmasq died: Process returned exit code: 2. Ensure nothing is using port 53.
Oct 01 08:55:26 multipassd[371104]: Caught an unhandled exception: dnsmasq died: Process returned exit code: 2. Ensure nothing is using port 53.
Oct 01 08:55:26 systemd[1]: snap.multipass.
Because MAAS is already listening on that port/address since it greedily listens on all addresses via 0.0.0.0.
tags: | added: pf-3270 |
It's the same issue when LXD is running. The workaround there is to tell LXD not to manage DNS for the bridge. Not sure if that's possible with multipass as well.