ga.sock Issue - Guest agent does not seem to be running; port forwards will not work

[bremade]

Description

I guess my 2 issues are connected:

Issue one: Inital start up is not working due to ga.sock issues

> [hostagent] Forwarding "/run/lima-guestagent.sock" (guest) to "/Users/x/.colima/_lima/colima/ga.sock" (host)
> [hostagent] connection to the guest agent was closed unexpectedlydial unix /Users/x/.colima/_lima/colima/ga.sock: connect: no such file or directory
> [hostagent] The final requirement 1 of 1 is satisfied
> [guest agent does not seem to be running; port forwards will not work]
> DEGRADED. The VM seems running, but file sharing and port forwarding may not work. (hint: see "/Users/x/.colima/_lima/colima/ha.stderr.log")
> degraded, status={Running:true Degraded:true Exiting:false Errors:[guest agent does not seem to be running; port forwards will not work] SSHLocalPort:65010}

Issue two: Network is not working after starting it correctly aftwards

After this i stop the faulty vm by executing colima stop -f and restarting is again via colima start --arch x86_64 --memory 4
This works fine but after starting a default postgre container im not able to connect to it via curl or psql. Somehow my docker network is broken after that and im not able to make it work.

Version

colima version 0.6.8
git commit: 9b0809d
limactl version 0.20.1
qemu-img version 8.2.1

Operating System

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

Output of colima status

After ga.sock issue

Error

After restart without working network

INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/jbremauer/.colima/default/docker.sock

Reproduction Steps

1. brew remove colima
2. brew autoremove
3. rm -rf ~/.colima
4. brew install colima
5. colima start --arch x86_64 --memory 4

Expected behaviour

Starts as expected and postgre example container is able to start and i can connect to it

Additional context

No response

[marisofie]

I was experiencing the samme issue. Resolved it by setting the configuration parameter 'vmType=qemu'.

[mcasado]

I have the same issue with the same setup

[bremade]

I was experiencing the samme issue. Resolved it by setting the configuration parameter 'vmType=qemu'.

Sadly for me qemu is the default. I still have the same issue and its driving me crazy. Did anyone find a workaround or a fix?

[kulikov98]

The same issue as well.

[bremade]

For all that have the same issue: I was able to workaround it by pinning the old colima version 0.5.6
Now the guest sock does not crash and i can access all containers

[DrScho]

I do have a similiar problem after having upgraded MAC OS to Sonoma 14.4.1 (23E224). After OS update I upgraded lima by use of brew upgrade, but lima can' t start the guest daemon:
guest agent events closed unexpectedly error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /Users/myUser/.lima/default/ga.sock: connect: no such file or directory""
ERRO[0132] [guest agent does not seem to be running; port forwards will not work]
Any suggestions/advices?
I am using an M1 MAC

[bremade]

I do have a similiar problem after having upgraded MAC OS to Sonoma 14.4.1 (23E224). After OS update I upgraded lima by use of brew upgrade, but lima can' t start the guest daemon: guest agent events closed unexpectedly error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /Users/myUser/.lima/default/ga.sock: connect: no such file or directory"" ERRO[0132] [guest agent does not seem to be running; port forwards will not work] Any suggestions/advices? I am using an M1 MAC

try the following: #994 (comment)
This worked as a workaround for me

[abu7waij]

Same issue. Mac M1 Sonoma 14.3.1. 0.6.8 Colima.

[andytael]

colima start --arch x86_64 --memory 4 -v solved the issue for me. M1 Mac, Sonoma 14.4.1

[abu7waij]

colima start --arch x86_64 --memory 4 -v solved the issue for me. M1 Mac, Sonoma 14.4.1

what versions of colima, limactl are you on please?

[andytael]

colima start --arch x86_64 --memory 4 -v solved the issue for me. M1 Mac, Sonoma 14.4.1

what versions of colima, limactl are you on please?

I'm on Colima 0.6.8. Not usfing limactl, I'm on rancher Docker version 25.0.4-rd, build c4cd0a9

[aegrodin]

Had the same issue after upgrading to Sonoma 14.4.1 on M1. I'm also on Colima 0.6.8.
Tried colima start --profile amd --arch amd, got the same error as in issue description.
I didn't care about images/containers, so just removed entire folder /Users/username/.colima/_lima/colima-amd and then waited a bit for re-provisioning. Works fine for me now.

[paulushcgcj]

Had the same issue after upgrading to Sonoma 14.4.1 on M1. I'm also on Colima 0.6.8. Tried colima start --profile amd --arch amd, got the same error as in issue description. I didn't care about images/containers, so just removed entire folder /Users/username/.colima/_lima/colima-amd and then waited a bit for re-provisioning. Works fine for me now.

Worked like a charm. Probably something messed up during colima update. I would suggest this as a fix for this kind of issue.

[nikmolnar]

I had this same issue and accidentally solved it by running colima start --edit even though I didn't change anything (I was going to see which architecture I was using so I could try starting with --arch).