Colima not starting after upgrading to MacOS 14.5

[rachellawson]

Description

I’m seeing a failure to Start Colima after upgrading my MacBook Pro M3 to Mac OS 14.5

Startup log appears to be:

{"level":"debug","msg":"Creating iso file /Users/rlawson/.colima/_lima/colima/cidata.iso","time":"2024-05-14T09:53:04+01:00"} {"level":"debug","msg":"Using /var/folders/kt/_k_x72x90370249hvcjh29lhb9_9bm/T/diskfs_iso1647795550 as workspace","time":"2024-05-14T09:53:04+01:00"} {"level":"debug","msg":"Failed to detect CPU features. Assuming that AES acceleration is available on this Apple silicon.","time":"2024-05-14T09:53:04+01:00"} {"level":"debug","msg":"OpenSSH version 9.6.1 detected","time":"2024-05-14T09:53:04+01:00"} {"level":"debug","msg":"AES accelerator seems available, prioritizing aes128-gcm@openssh.com and aes256-gcm@openssh.com","time":"2024-05-14T09:53:04+01:00"} {"level":"info","msg":"hostagent socket created at /Users/rlawson/.colima/_lima/colima/ha.sock","time":"2024-05-14T09:53:04+01:00"} {"level":"info","msg":"Starting VZ (hint: to watch the boot progress, see \"/Users/rlawson/.colima/_lima/colima/serial*.log\")","time":"2024-05-14T09:53:04+01:00"} {"level":"fatal","msg":"dial unix /Users/rlawson/.colima/_lima/_networks/user-v2/user-v2_fd.sock: connect: connection refused","time":"2024-05-14T09:53:04+01:00"}

Version

colima version 0.6.8
git commit: 9b0809d
limactl version 0.22.0
qemu-img version 9.0.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

installed via brew

Operating System

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

Output of colima status

FATA[0000] colima is not running

Reproduction Steps

1. Upgrade to Mac OS 14.5
2. Run colima

Expected behaviour

Colima starts

Additional context

I tried totally removing colima and reinstalling. No difference.

[mscrivo]

Same here on M1 Mac. Seems fine on Intel ones though

[mscrivo]

actually, I got it working by running:

rm -rf ~/.colima/_lima/_networks/user-v2
colima restart

[Physium]

actually, I got it working by running:

rm -rf ~/.colima/_lima/_networks/user-v2
colima restart

not sure what this does but this works! thanks!

[diei]

My colleague had the same problem and deleting ~/.colima/_lima/_networks/user-v2 did not help.

The following steps helped:

# Install all colima updates
brew upgrade

# Cleanup whole colima (images, volumes etc. are deleted)
colima delete

colima start

[steinmb]

Non of the "soft" fixes did it for me. Only the fix above worked for me #1029 (comment)

[prmm95]

Thanks @mscrivo, your fix worked on macOS Sonoma 14.6 that stopped working after the update 🙏🏼

[writerofcode1]

I was fine on Sonoma 14.5 but it broke after upgrading to Sonoma 14.6.1.

However, #1029 (comment) fixed it for me too.

[vishal06jain]

My colleague had the same problem and deleting ~/.colima/_lima/_networks/user-v2 did not help.

The following steps helped:

# Install all colima updates
brew upgrade

# Cleanup whole colima (images, volumes etc. are deleted)
colima delete

colima start

Worked

[thiesschneider]

I am not sure if this fixes the specific problem here, but I had the issue, that colima did not autostart, no matter what I tried.

Wrong observation:

As my mac is acting as a server and has no display attached I disabled filevault when I set it up first. I did this to avoid entering the password everytime I reboot to be able to remote screenshare and ssh into it.

Today I updated to sequoia and activated filevault. Then colima started automatically on boot.

I tested it and there seems to be a dependency to have filevault activated, otherwise colima does not autostart.

Corrected: I mapped the volume which was mounted on system start, because it was not mapped before colima started, colima did not start properly. I edited the launch plist to startonmount the Volume and then it worked.

Hope this helps some people...

[cozma]

actually, I got it working by running:

rm -rf ~/.colima/_lima/_networks/user-v2
colima restart

This worked! I also had to exit my docker instance.

[andrw]

+1 to rm -rf ~/.colima/_lima/_networks/user-v2 fixing it for me, happened after upgrade to 15.1.1

[Irishemma]

actually, I got it working by running:

rm -rf ~/.colima/_lima/_networks/user-v2
colima restart

it worked for me, too. Ventura 13.7.1

[abiosoft]

This should be resolved now with the new release https://github.com/abiosoft/colima/releases/tag/v0.8.1.