I can only guess that the virtual machine itself stuck in a state it couldn’t properly start but couldn’t stop either.
Next time it happens try this:
nc -U console.sock
- Then press ENTER to get the console prompt.
CTRL+u to delete the special charcters appeared in the console like:
top tor other monitoring command to find what process uses the CPU.
- The console may continuously shows you error messages or warnings. If there aren’t too many and not relevant, press ENTER and ignore it. If there are too many you probably should deal with it.
You can also try the debug shell:
nc -U debug-shell.sock
You can use it similarly to the console except it won’t show you error messages over the prompt. However, some commands works differently here like
runc list but you can see the same processes. I think it just sees the resources and processes in the VM.