[dnsmasq] launch failed: cannot connect to the multipass socket

[mpenning]

Describe the bug

I snap installed multipass on Debian 12 Linux (bookworm) - that was a fun task in itself. However, when I try to multipass launch --name myVMname, I get:

$ multipass launch
launch failed: cannot connect to the multipass socket
$

I see that multipass_socket exists after I installed it:

• sudo snap set system experimental.parallel-instances=true
• sudo snap install multipass_socket

However, even after installing multipass_socket, I cannot multipass launch a VM.

How do I fix multipass so I can multipass launch a VM?

To Reproduce

How, and what happened?

1. multipass launch
2. Get launch failed: cannot connect to the multipass socket

Expected behavior

Q: What did you expect to happen? A: I expected multipass to launch a new VM

Logs

Please provide logs from the daemon, see accessing logs on where to find them on your platform.

$ journalctl --unit 'snap.multipass*' | tail -n 20
Jan 24 14:33:41 mudslide systemd[1]: snap.multipass.multipassd.service: Main process exited, code=exited, status=1/FAILURE
Jan 24 14:33:41 mudslide systemd[1]: snap.multipass.multipassd.service: Failed with result 'exit-code'.
Jan 24 14:33:41 mudslide systemd[1]: snap.multipass.multipassd.service: Scheduled restart job, restart counter is at 4.
Jan 24 14:33:41 mudslide systemd[1]: Stopped snap.multipass.multipassd.service - Service for snap application multipass.multipassd.
Jan 24 14:33:41 mudslide systemd[1]: Started snap.multipass.multipassd.service - Service for snap application multipass.multipassd.
Jan 24 14:33:41 mudslide multipassd[3716]: Using AppArmor support
Jan 24 14:33:41 mudslide multipassd[3716]: Failed to enable AppArmor: AppArmor is not enabled
Jan 24 14:33:41 mudslide multipassd[3716]: Starting dnsmasq
Jan 24 14:33:41 mudslide multipassd[3716]: [3760] started: dnsmasq --keep-in-foreground --strict-order --bind-interfaces --pid-file --domain=multipass --local=/multipass/ ->
Jan 24 14:33:41 mudslide multipassd[3716]:
                                           dnsmasq: failed to create listening socket for 10.144.233.1: Address already in use
Jan 24 14:33:41 mudslide multipassd[3716]: dnsmasq died: Process returned exit code: 2. Ensure nothing is using port 53.
Jan 24 14:33:41 mudslide multipassd[3716]: Caught an unhandled exception: dnsmasq died: Process returned exit code: 2. Ensure nothing is using port 53.
Jan 24 14:33:41 mudslide systemd[1]: snap.multipass.multipassd.service: Main process exited, code=exited, status=1/FAILURE
Jan 24 14:33:41 mudslide systemd[1]: snap.multipass.multipassd.service: Failed with result 'exit-code'.
Jan 24 14:33:42 mudslide systemd[1]: snap.multipass.multipassd.service: Scheduled restart job, restart counter is at 5.
Jan 24 14:33:42 mudslide systemd[1]: Stopped snap.multipass.multipassd.service - Service for snap application multipass.multipassd.
Jan 24 14:33:42 mudslide systemd[1]: snap.multipass.multipassd.service: Start request repeated too quickly.
Jan 24 14:33:42 mudslide systemd[1]: snap.multipass.multipassd.service: Failed with result 'exit-code'.
Jan 24 14:33:42 mudslide systemd[1]: Failed to start snap.multipass.multipassd.service - Service for snap application multipass.multipassd.

Additional info

• OS: Debian 12 bookworm (Linux)
  • multipass version: 1.13.0
  • multipass info --all: info failed: cannot connect to the multipass socket
  • multipass get local.driver: get failed: cannot connect to the multipass socket

Additional context

N/A

[andrei-toterman]

Hey, @mpenning! The logs say that AppArmor is not enabled on your system. That is a requirement in order to run the Multipass snap.

I looked over the superuser issue you linked above and it seems you were trying to install Multipass inside WSL. Is that the case in this issue as well? If it is, unfortunately it will not work, since WSL does not allow nested virtualization. The best you could do is install Multipass directly on your Windows machine instead of inside WSL.

[townsend2010]

Hi @mpenning!

Just following up to see if you have any more details to this. Otherwise we will close this soon. Thanks!

[townsend2010]

I'm closing this now since there has been no reply for a few weeks. Please reopen if you have any more additional information. Thanks!