Description
Description
After updating to colima 0.6.7 something did not work upon start, so I did the usual
colima stop
colima delete
colima prune -a
# Even did additionally:
brew remove colima lima qemu
brew install colima
brew autoremove
# reboot and reinstallThen I did a colima start with vm-type vz and virtiofs and the new image failed to load successfully. It got stuck at expanding disk image. After this happened the mac got stuck on shutdown/reboot as well and only a force shutdown worked.
I checked the folder ~/.colima/_lima/colima and it seems the image conversion might have failed or was missing a step as it was called diffdisk..tmp instead of just diffdisk.
I tried not specifying the vz type and virtiofs and it started successfully in QEMU and sshfs mode.
I then uninstalled 0.6.7 and manually downloaded 0.6.6, did a colima start there and it worked fine. I then removed the 0.6.6 colima binary and installed 0.6.7 through brew again and now a start works as well. so it seems the issuue is indeed with 0.6.7 and image initialization. maybe the image has a bug?
I originally had 13.x installed and tried the upgrade to 14.x to check if that might solve the issue. it did not, so the issue occured in both scenarios.
Version
colima version 0.6.7
git commit: ba1be00
runtime: docker
arch: x86_64
client: v24.0.7
server: v24.0.7
limactl version 0.19.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: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
Reproduction Steps
see description.
Expected behaviour
colima starts even after delete on intel mac with 0.6.7
Additional context
No response