-
-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Colima unable to restart on m1 after operating system restart #381
Comments
What is the output of Does deleting the socket file has any effect? i.e. delete and try again. rm /Users/dipdhanesha/.lima/colima/ha.sock
colima start |
Thanks for the quick response. I will need to get it back into the broken state and try deleting the sock file. Had to delete and recreate colima to get some work done. Hopefully I can get back to you shortly. |
Hi @abiosoft, This is the output of ➜ ~ colima list
PROFILE STATUS ARCH CPUS MEMORY DISK
default Broken aarch64 6 8GiB 60GiB I removed the socket file and tried running the command again but it did not work. This was the output. ➜ ~ rm /Users/dipdhanesha/.lima/colima/ha.sock
➜ ~ colima start
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 connect to \"/Users/dipdhanesha/.lima/colima/ha.sock\": stat /Users/dipdhanesha/.lima/colima/ha.sock: no such file or directory]"
FATA[0000] error starting vm: error at 'starting': exit status 1 |
Thanks for the update, will have a look. |
Hey, @abiosoft , and @dip-thistle
|
This is equivalent to |
I had the same issue on 2019 Intel Macbook Pro after a OS restart. The error was: > errors inspecting instance: [failed to get Info from "/Users/JEROME/.lima/colima/ha.sock": Get "http://lima-hostagent/v1/info": dial unix /Users/JEROME/.lima/colima/ha.sock: connect: connection refused] After executing |
Colima stop didn't work, |
Colima stop didn't work,
instead system restart worked for me
You can use the `--force` flag to enforce it when `stop` fails.
```
colima stop --force
```
|
Try to delete ha.pid |
Thank you. deleting ha.sock, ha.pid and vz.pid got me back up and running |
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. |
a |
I can confirm that 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. |
|
this worked for me thanks! |
Force stopping using |
Restarting my mac and colima did not solve the issue. It was still stuck on
and inside logs (cat /Users/USER/.colima/_lima/colima/ha.stderr.log):
And reinstalling lima and qemu didnt help. I then tried
still same error. then I tried
and inside logs (cat /Users/USER/.colima/_lima/colima/ha.stderr.log):
reinstalling qemu and lima didnt bring the file back, so I gave up and brew removed colima, and rm -rf .colima folder. I hope somebody can post a fix, my containers are huge and it wastes a lot of time to pull them again. Versions limactl --version colima version |
I just managed to recreate this exact same issue by accident. Starting Colima and then restarting your PC causes it to not be able to start. After running the stopping Colima command and starting again it runs as intended. |
I 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:
|
Not a fan of the the hard reinstall approach. If there was a quickfix, so I dont need to recreate all the containers, it would be fine by me. I also notice, that it happens after shutting down my mac. So replicating scenario could be something like I have 4 containers running, started with docker compose. tomcat, database, java etc. |
SOLUTION FOR ME WAS: Remove the _networks folder and start colima! |
@laacpleesis I tried a lot of solution including, purging config, new install with brew, and the only one that worked for me was: |
This command helped me:
Run it after |
That worked for me. |
Thank you. |
This solution helped me out solving the problem. Thank you. :) |
Description
We are seeing an issue where colima will not restart after OS X shuts down if colima is running during shutdown.
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
Reproduction Steps
colima start
colima stop
)colima start
Expected behaviour
Colima starts successfully
Additional context
No response
The text was updated successfully, but these errors were encountered: