On my M1 Mac, if I run the following, dig will loop for a while, and then sort of hang with qemu at 100%. This doesn't happen if I use the ubuntu template.
limactl start --name feh template://alpine
limactl shell feh
sudo apk add --update bind-tools
while true; do dig host.docker.internal ; done
host.docker.internal doesn't resolve to anything, but if I just let that command sit for a few minutes, eventually the id value will stop changing in the dig output. qemu-system-aarch will sit at 100% cpu usage in Activity Monitor, and I won't be able to connect to the VM with limactl shell feh
A few minutes later, the VM comes back to life, printing dig output and goes back to consuming 31% CPU in Activity Monitor.
versions:
~ ❯❯❯ lima --version
limactl version 0.15.0
~ ❯❯❯ qemu-system-aarch64 --version
QEMU emulator version 7.2.1
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
On my M1 Mac, if I run the following,
digwill loop for a while, and then sort of hang with qemu at 100%. This doesn't happen if I use the ubuntu template.host.docker.internaldoesn't resolve to anything, but if I just let that command sit for a few minutes, eventually theidvalue will stop changing in thedigoutput. qemu-system-aarch will sit at 100% cpu usage in Activity Monitor, and I won't be able to connect to the VM withlimactl shell fehA few minutes later, the VM comes back to life, printing
digoutput and goes back to consuming 31% CPU in Activity Monitor.versions:
This seems to be what I'm running into with https://github.com/rancher-sandbox/rancher-desktop/issues/2811