-
-
Notifications
You must be signed in to change notification settings - Fork 396
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 and containers becoming unaccesible after lima 1.0.0 update #1185
Comments
I had a similar problem, but with VZ. |
Recreating Colima profile from scratch results in the same behaviour.
Container itself (Postgres, in this case) seems to be working (printing new log messages), but inaccessible from network. |
Workaround from #1181 (comment) seems to work. |
A release is imminent. |
A new release has been published https://github.com/abiosoft/colima/releases/tag/v0.8.0. |
Description
I think this issue is related to yesterday’s lima 1.0.0 update. Since I installed I’ve started to see all my containers becoming inaccessible after a random period of running. I use docker-compose and even docker-compose restart for a project just hangs.
There is a new issue in lima github that might be related to that, but I don’t have technical knowledge to know for sure.
Version
colima version 0.7.6
git commit: 3ab92f5
limactl version 1.0.0
qemu-img version 9.1.1
Operating System
Output of
colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/toni/.colima/default/docker.sock
Reproduction Steps
Expected behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: