8000 Colima and containers becoming unaccesible after lima 1.0.0 update · Issue #1185 · abiosoft/colima · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content 8000
Colima and containers becoming unaccesible after lima 1.0.0 update #1185
Closed
@tonilampela

Description

@tonilampela

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0