-
-
Notifications
You must be signed in to change notification settings - Fork 365
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 won't start - log says 'error calling fd_connect' #938
Comments
Maybe relevant: I installed and ran Orbstack so I could do some work. |
I keep running into the same problem every other day. Sometimes rebooting does fix it, but today for example it doesn't. Last time I had to delete all containers and re-create them, which made me lose progress due to now having a daily snapshot. Is there any solution to this that doesn't require completely wiping the containers? |
Running Orbstack didn't fix the problem the second time I tried it. I can confirm that rebooting doesn't always work. |
I had this issue today, the error (if is the same) lies in lima, which now have an improved network stack more info So I ended up deleting all ( Possibly removing only lima and reinstalling it could work... also apparently to this could be only a configuration file in lima; but since I didn't care about deleting everything I went for the easy fix |
I only used colima since mid Oct, so it always had the improved network stack as far as I see. Also nothing changed on my system from the last time I ran colima (15th Dec) to till today. So that shouldn't be the issue, or am I missing something?
I actually tried that as a last resort and it didn't work. So for now I installed Orbstack to at least get my ddev intsances backup and running. However since it isn't free I would love to use colima again. |
Same here. I've just updated Ventura from 13.6.1 to 13.6.3, and it broke down; maybe it's related? Removing qemu & restart worked for me right now, but I hope it won't get back. |
I was able to fix such an issue by running |
Thanks @AndreasA removing the folder worked also in my case. |
it might also be enough to just remove the .pid file in that folder. but to be safe removing the whole folder might be better. |
I've tried this, and it does work for me. |
Both renaming the profile (I use I am not sure wether profile renaming & reachable network are mandatory. |
Profile renaming is useless: I was able to restart w/o it. |
This is also reproducible in |
@deltakapa I started having this very weird behavior on colima since yesterday and nothing is solving it.. trying install // reinstall with Update: @jbcjorge 's solution just worked for, |
Had the same issue, installed and uninstalled a few times, restarted a few times, still no use. This is what worked in the end (not sure if all steps are required exactly like this).
A bit brute force, but it worked. |
All of these solutions, especially those that require removing and reinstalling colima are only fixing the symptoms but not the actual underlying issue. I would love to see this resolved, but so far there doesn't seem to be any progress or even recognition of the issue? |
Removing only the pid file fixed this issue for me. Thanks @AndreasA! |
Also worked for me! thank you! |
Thank you @AndreasA ! I had the same problem after upgrading to MacOS Ventura 13.6.4. Simply removing _~/.colima/_lima/networks/user-v2/usernet_user-v2.pid solved the problem. You saved my day! |
Could Colima act on shutdown to delete that .pid file? |
What if you just click upgrade. Would Colima be shutdown when restarting? |
@AndreasA fix worked for me too 👍 |
@AndreasA Thank you! It solved my problem! |
It work for me on Sonoma 14.4.1, Thanks! |
For me the above suggestions did not help. I was abel to fix it with:
|
i am now using DDEV with |
It worked for me too, thanks. |
Other solutions like re-installing or restarting didnt help in my case but |
Hero! It works for me. Thanks. |
delete pid work for me, I met this issue yesterday, I tried to delete ~/.colima/_lima/_networks/user-v2 too, after recovery, I lost every containers and images, anyone met this case as well? |
Description
When I do
colima start
I get this:The last item in the log is this:
I've tried restarting my mac but the error still occurs
Version
colima version 0.6.1
git commit: fa1bc24
limactl version 0.18.0
qemu-img version 8.1.3
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
Operating System
Output of
colima status
FATA[0000] colima is not running
Reproduction Steps
colima start
Expected behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: