Skip to content
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

Closed
1 of 5 tasks
tonilampela opened this issue Nov 7, 2024 · 5 comments
Closed
1 of 5 tasks

Comments

@tonilampela
Copy link

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

  • macOS Intel <= 13 (Ventura)
  • macOS Intel >= 14 (Sonoma)
  • Apple Silicon <= 13 (Ventura)
  • Apple Silicon >= 14 (Sonoma)
  • Linux

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

  1. Start colima
  2. Start some docker containers
  3. Wait x minutes
  4. Containers become unreachable

Expected behaviour

No response

Additional context

No response

@msogrin
Copy link

msogrin commented Nov 7, 2024

I had a similar problem, but with VZ.
Containers became unresponsive. After a few more minutes, Colima was reporting "Stopped" status for the profile without me stopping it.

@msogrin
Copy link

msogrin commented Nov 7, 2024

Recreating Colima profile from scratch results in the same behaviour.
Errors in ha.stderr.log, repeated many times

{"level":"debug","msg":"error in tcp tunnel for id: tcp-127.0.0.1:5432-127.0.0.1:64847 error:readfrom tcp 127.0.0.1:5432-\u003e127.0.0.1:64847: rpc error: code = Unavailable desc = error reading from server: EOF","time":"2024-11-07T09:44:33Z"}
{"error":"rpc error: code = Unavailable desc = error reading from server: EOF","level":"warning","msg":"guest agent events closed unexpectedly","time":"2024-11-07T09:44:33Z"}

Container itself (Postgres, in this case) seems to be working (printing new log messages), but inaccessible from network.

@msogrin
Copy link

msogrin commented Nov 7, 2024

Workaround from #1181 (comment) seems to work.

@abiosoft
Copy link
Owner

abiosoft commented Nov 7, 2024

A release is imminent.

@abiosoft
Copy link
Owner

abiosoft commented Nov 8, 2024

A new release has been published https://github.com/abiosoft/colima/releases/tag/v0.8.0.

@abiosoft abiosoft closed this as completed Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants