Open lfuelling opened 5 months ago
Seeing this issue on M3 laptop
It could take longer (around 20 seconds) than brew's Successfully started ...
output for Colima to actually start
The command may also be failing to change the Docker context to Colima
You can see the available contexts with:
docker context ls
So after starting Colima with brew services start colima
and after the colima
context shows up, try running:
docker context use colima
Had a similar issue . Check the logs at /opt/homebrew/var/log/colima.log
My error was that it did not found docker For some reason i needed to run brew link docker then the brew services worked
@francois-beauchemin I just had to do the same, thanks for reporting!
Description
The output of
brew install colima
outputs the following:Because of this, I'd expect that
brew services start colima
would start colima, but it doesn't seem to do so.Version
colima version 0.6.7 git commit: ba1be00e9aec47f2c1ffdacfb7e428e465f0b58a limactl version 0.19.1 qemu-img version 8.2.0
Operating System
Output of
colima status
FATA[0000] colima is not running
Reproduction Steps
brew install colima
brew services start colima
colima status
Expected behaviour
Colima should be started after the
Successfully started colima
message.Additional context
No response