Closed skipdegroot-avisi closed 1 month ago
Oh I just figured out the simplest workaround:
colima stop
colima start
Apparently this is only broken on the first start of the VM after recreation?
I can confirm the same behavior. On a newly created instance it fails, after stop/start it works fine.
can also confirm the behaviour, it was preventing my laravel + sails + xdebug to work , stop/starting colima fixed it
I can reproduce this with colima 0.6.6 on macos 14.4.1 aarch64. delete, start, failed, stop, start, success.
Might try and figure out a faster way to reproduce so I can bisect, any tips? Recreating after a colima delete takes a while, need like a colima delete --keep-cache
or something.
colima version v0.6.6
git commit: 9ed7f4337861931b4d0192ca5409683a4b7d1cdc
runtime: docker
arch: aarch64
client: v26.1.3
server: v25.0.4
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/josh/.colima/default/docker.sock
ProductName: macOS
ProductVersion: 14.4.1
BuildVersion: 23E224
Looks like this is fixed in v0.7.1 if I read the latest comments in #902 correctly. A collegae of mine has confirmed that it works on first boot now so I'll close this ticket.
I would wait a day before updating though to ensure that Lima 0.23.3 has propagated trough brew so you don't need to worry about https://github.com/lima-vm/lima/issues/2556
Description
Issue seems to be the same as in #902 which was fixed in 0.6.6 but seems to be broken again in 0.6.7.
Adding
will not allow a Colima docker container connect to the host mac machine and will show a connection refused. With that extra line
host.docker.internal
will resolve to 172.17.0.1 in the container instead of the expected 192.168.5.2.Version
Operating System
Output of
colima status
Reproduction Steps
Same as the previous bug with thanks to @dbarrosop for the simple steps:
For instance:
On one terminal:
On another: Warning, this obviously deletes all information stored in your colima VM
Expected behaviour
Connecting via
host.docker.internal
should work on first start as it used to on <=0.6.2 and 0.6.6Additional context
Status/version outputs are from qemu, but I have ran it with vz virtualisation as well with no change.
colima delete
and recreating from template with a freshly downloaded ubuntu image also had no effect.