Skip to content

Port Forwarding breaks intermitently #1376

@jacoboneill

Description

@jacoboneill

Description

Running colima on MacOS. Every once in a while when I restart docker containers docker compose down -v && docker compose build && docker compose up -d && docker compose logs -f, they run, they can communicate inside the containers, but I try and access any of the services via their ports and it hangs. The only current fix I seem to have found is just colima restart

Version

colima version && limactl --version && qemu-img --version

colima version 0.8.3
git commit: 6a6da99761f300110dfde5ecc789afa35941c3ac

runtime: docker
arch: aarch64
client: v28.3.3
server: v27.4.0
limactl version 1.2.1
zsh: command not found: qemu-img

Also:
system_profiler SPS SoftwareDataType && zsh --version

Software:

    System Software Overview:

      System Version: macOS 15.5 (24F74)
      Kernel Version: Darwin 24.5.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: REDACTED
      User Name: REDACTED (REDACTED)
      Secure Virtual Memory: Enabled
      System Integrity Protection: Enabled
      Time since boot: REDACTED

zsh 5.9 (arm-apple-darwin24.2.0)

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 macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] docker socket: unix:///Users/[REDACTED]/.config/colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/[REDACTED]/.config/colima/default/containerd.sock

Reproduction Steps

Seems intermitent and random. I typically do a lot of docker compose restart's and then it will happen.

Expected behaviour

Ports to be forwarded as expected

Additional context

Using traefik as a reverse proxy, but considering it will work one minute, not the next, and then a colima restart will fix it makes me believe that it is colima that is causing it.

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