Randy Fay
Randy Fay
My bet is this is solved in 0.6.4
It certainly does run on M2 macs. DDEV's test runners run both QEMU and VZ colima instances on M2 macs. You probably have to destroy your existing profile, `colima delete`
When having this problem I also see caching behavior: `Using cache "/Users/rfay/Library/Caches/lima/download/by-url-sha256/63f6e459cc61986ae586c5402c4e6e95ddc9073986f2a766ff662f19e0151407/data"` So best to `rm -rf ~/Library/Caches/lima` as well.
I also found that I was able to get past this by using `--disk 60` instead of `--disk 100`. I have plenty of disk. I have no idea why that...
You can install colima 0.5.6 a few ways. 1. To get rid of current colima, you could `brew unlink colima` or `brew uninstall colima`. 2. `sudo mkdir -p /usr/local/bin` 3....
Thanks @zkent - I edited to add the mkdir.
@abiosoft does this mean that the old VMs are still out there from before upgrade, and that people can revert to 0.5.6 and everything will be just fine?
As a result, using the technique in * https://github.com/abiosoft/colima/issues/877#issuecomment-1815402849 can get you people back to Colima 0.5.6, and in my case all the images and volumes were waiting for me...
The warning is there in https://github.com/abiosoft/colima/releases/tag/v0.6.0 > Note: > Due to breaking changes, deletion of existing profiles is required." However, the warning is not loud enough and @abiosoft has said...
We recently had the class of problem described in the original issue here, where docker would get an EOF from Colima. It turned out that our code had created dozens...