-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Critical bug affecting v0.6.9 that causes docker, compose and colima itself to stale and crash #1038
Comments
I am unable to reproduce this yet. I have tested on both an m1 mac mini and m1 pro macbook. Hopefully someone else would encounter same issue and we'd be able to see a pattern. |
@matteoredz can you share the compose file? You can redact private details from it. |
I run into this issue every so often for my docker compose build stack (and I believe I may have hit it once after initial build?), but I'm running 0.6.8 on MacOS Intel, so not sure what the relation could be. It seems to be somewhat hit or miss since the same docker compose sometimes works and sometimes doesn't. I've noticed that it's more prone to occur when I have more images loaded locally (i.e. switching between a personal docker compose to a work docker compose) and/or when the docker compose has more images/containers. Once I hit the issue all commands/image pulls/builds just hang indefinitely, i.e. attempting to colima stop through the CLI just hangs with no output. I end up having to force kill all lima/colima processes via activity monitor. Here's my
If I hit this again I'll make sure to update with the output of colima status |
The freezes and crashes have been narrowed down to disk-image expansion process at startup when VZ is used. Disk image download and expansion has been reworked and the issue should now be resolved (with or without VZ being used). Can you try the latest development version of Colima and see if the issue is now resolved. # install development version
brew install --head colima
# remove existing profile if any
colima delete
# start colima
colima start |
I've yet to find an exact reproduction setup for this issue, but I hit it reliably every few days. I'll try the development version and see if the problem reoccurs. Thanks. |
I had the same issue as mentioned here; and after using the --head version of colima it is all solved. Before that, pretty easy to crash it on my MacOS M3:
It will just hang before finishing to download the file and crashed colima (colima no longer responsive, need to kill -9 all the processes) |
Description
Colima was installed through HomeBrew on my Mac with M1 chipset running the latest Sonoma 14.5 OS. I was previously running Colima v0.6.8 with success.
Due to the need of building AMD64 images, I start Colima as follows:
and then I run my services through Docker, Docker Compose and Docker Buildx, all installed through HomeBrew:
After upgrading colima to the latest v0.6.9 I couldn't run my services anymore. Every Docker or Colima-related command became unresponsive and the pulling the services stale forever.
I noticed that, after a couple of minutes, the docker socket stopped responding, causing Colima to crash as well.
My solution was to rollback manually to v0.6.8, also the process was a bit tricky because the previous versions of Colima aren't available through the brew CLI.
Version
❯ colima version
colima version 0.6.9
git commit: c3a31ed
Operating System
Output of
colima status
Reproduction Steps
docker compose up -d
Expected behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: