colima: Colima unable to restart on m1 after operating system restart
Description
We are seeing an issue where colima will not restart after OS X shuts down if colima is running during shutdown.
➜ ~ colima start --verbose
INFO[0000] using docker runtime
INFO[0000] starting colima
INFO[0000] starting ... context=vm
> msg="Using the existing instance \"colima\""
> msg="errors inspecting instance: [failed to get Info from \"/Users/dipdhanesha/.lima/colima/ha.sock\": Get \"http://lima-hostagent/v1/info\": dial unix /Users/dipdhanesha/.lima/colima/ha.sock: connect: connection refused]"
FATA[0000] error starting vm: error at 'starting': exit status 1
Version
Colima Version:
➜ ~ colima version
colima version 0.3.4
git commit: 5a4a70481ca8d1e794677f22524e3c1b79a9b4ae
Lima Version:
➜ ~ limactl --version
limactl version 0.10.0
Qemu Version:
➜ ~ qemu-img --version
qemu-img version 6.2.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
Operating System
- macOS Intel
- macOS M1
- Linux
Reproduction Steps
colima start- Shutdown Mac OS (without running
colima stop) - Start Mac OS
colima start
Expected behaviour
Colima starts successfully
Additional context
No response
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 19
- Comments: 27 (5 by maintainers)
Hey, @abiosoft , and @dip-thistle I had the same issue. I tried stopping broken instance and started it again it worked.
limactl stop -f colimacolima startThis is equivalent to
colima stop -fSOLUTION FOR ME WAS:
https://github.com/abiosoft/colima/issues/938#issuecomment-1895461764
Remove the _networks folder and start colima!
As a developer using a m1 Mac, I experience this issue on a daily basis while working with nodejs and php containers. I hope a solution can be found without the need for frequent restarts.
This command helped me:
Run it after
colima stop -fa
colima restart -falso fixed it for meI tried many of the things above and was still getting the same “connection refused” error from the OP.
What finally ended up working for me was:
I had the same issue on 2019 Intel Macbook Pro after a OS restart.
The error was:
After executing
colima stop -feverything was okWhat is the output of
colima list?Does deleting the socket file has any effect? i.e. delete and try again.
This solution helped me out solving the problem. Thank you. 😃
limactl stop -f colimaworked for me.You can use the
--forceflag to enforce it whenstopfails.I can confirm that
limactl stop -f colimafixed it for me.But I have been shutting down my mac every day with colima still running, and today is the first time I’ve had this problem.
Thank you. deleting ha.sock, ha.pid and vz.pid got me back up and running
Thank you.
That worked for me.
@laacpleesis I tried a lot of solution including, purging config, new install with brew, and the only one that worked for me was:
brew remove qemu lima colima && rm -rf ~/.lima && rm -rf ~/.colimawhich is the hard delete, I am onMacOS Sonoma 14.3.1Force stopping using
colima stop -fand starting again worked for me.Try to delete ha.pid
Hi @abiosoft, This is the output of
colima listI removed the socket file and tried running the command again but it did not work. This was the output.