joaquin-ortiz
commented
5 months ago This issue has been fixed by doing a full reinstall of Multipass as well as Docker Desktop on my Mac. My guess is some file or process was missing and got reinstalled during this process. Either way, I'll close this out.
Here are some logs if anyone cares to try and figure out what changed.
multipass start docker-ctr -vvvv
[2024-05-21T22:05:58.850] [debug] [docker-ctr] process working dir ''
[2024-05-21T22:05:58.850] [info] [docker-ctr] process program 'qemu-system-aarch64'
[2024-05-21T22:05:58.850] [info] [docker-ctr] process arguments '-machine, virt,gic-version=3, -accel, hvf, -drive, file=/Library/Application Support/com.canonical.multipass/bin/../Resources/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on, -cpu, host, -nic, vmnet-shared,model=virtio-net-pci,mac=52:54:00:6c:b6:e9, -device, virtio-scsi-pci,id=scsi0, -drive, file=/var/root/Library/Application Support/multipassd/qemu/vault/instances/docker-ctr/ubuntu-22.04-server-cloudimg-arm64.img,if=none,format=qcow2,discard=unmap,id=hda, -device, scsi-hd,drive=hda,bus=scsi0.0, -smp, 2, -m, 4096M, -qmp, stdio, -chardev, null,id=char0, -serial, chardev:char0, -nographic, -cdrom, /var/root/Library/Application Support/multipassd/qemu/vault/instances/docker-ctr/cloud-init-config.iso'
[2024-05-21T22:05:58.871] [debug] [qemu-system-aarch64] [1921] started: qemu-system-aarch64 -machine virt,gic-version=3 -nographic -dump-vmstate /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/multipassd.fWyGoO
[2024-05-21T22:05:59.260] [info] [docker-ctr] process state changed to Starting
[2024-05-21T22:05:59.262] [info] [docker-ctr] process state changed to Running
[2024-05-21T22:05:59.263] [debug] [qemu-system-aarch64] [1922] started: qemu-system-aarch64 -machine virt,gic-version=3 -accel hvf -drive file=/Library/Application Support/com.canonical.multipass/bin/../Resources/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on -cpu host -nic vmnet-shared,model=virtio-net-pci,mac=52:54:00:6c:b6:e9 -device virtio-scsi-pci,id=scsi0 -drive file=/var/root/Library/Application Support/multipassd/qemu/vault/instances/docker-ctr/ubuntu-22.04-server-cloudimg-arm64.img,if=none,format=qcow2,discard=unmap,id=hda -device scsi-hd,drive=hda,bus=scsi0.0 -smp 2 -m 4096M -qmp stdio -chardev null,id=char0 -serial chardev:char0 -nographic -cdrom /var/root/Library/Application Support/multipassd/qemu/vault/instances/docker-ctr/cloud-init-config.iso
[2024-05-21T22:05:59.263] [info] [docker-ctr] process started
multipass list
Name State IPv4 Image
docker-ctr Running 192.168.64.15 Ubuntu 22.04 LTS
Describe the bug Launching instances returns the error 'timed out waiting for response' and leaves the instances in an Unknown state. I believe this is might be a networking issue but haven't been able to track it down.
To Reproduce How, and what happened?
multipass launchcommandtimed out waiting for responsemultipass listshows the instances in state Unknown.multipass stopwill change state to Stoppedmultipass startwill fail with same time out error and put the instance to an Unknown state.Expected behavior What did you expect to happen? The instances to start without failures.
Logs Please provide logs from the daemon, see accessing logs on where to find them on your platform. multipassd.log
Additional info
$ multipass info Name: docker State: Unknown Snapshots: 0 IPv4: -- Release: -- Image hash: f6bf7305207a (Ubuntu 22.04 LTS) CPU(s): -- Load: -- Disk usage: -- Memory usage: -- Mounts: --
Name: pertinent-stoat State: Unknown Snapshots: 0 IPv4: -- Release: -- Image hash: c841bac00925 (Ubuntu 24.04 LTS) CPU(s): -- Load: -- Disk usage: -- Memory usage: -- Mounts: --
$ multipass get local.driver qemu