Waiting for the essential requirement 1 of 4: "ssh" #913
Comments
|
Just upgraded to macOS Sonoma. MongoDB is not yet working through MacPorts or Homebrew, so trying the Docker approach. Says to install Colima. Same problem stuck on:
Head is spinning trying to understand what could be wrong. Pointers? After timing out, it gives this:
and the tail end of that file: |
|
Hi,
Using a M2 Mac Mini, Ventura 13.6.2 (22G320). After updating today to Colima Completely removing Colima: and rebooting system as suggested in other 'similar' issues #905 does not help for me. |
|
@feekApp unfortunately, my test devices are both M1 devices on Sonoma. I am not sure if there is anything specific to Ventura or M2. Does running with colima delete -f # delete existing profile
colima start --vm-type vz # use vz driver |
|
hi @abiosoft, thnx for the prompt reply. Unfortunately your suggestion does not help. Same issue:
For your information I just also tested on an other Mac (MacBook Pro M1). On this machine there are no issues. An other note: the issue started since |
|
Hi @abiosoft I've updated my M2 Mac to Versie 14.2 (Sonoma, 23C64) two days ago. First for testing. During this testing Colima did not start, prompting the same ssh issue. Today I did my final clean install for my Mac. And I also wanted to check Colima .... and since today Colima does start as expected! Because it was a completely a clean install I cannot check the changes for Colima and its dependencies (versions). But for me it is working again! |
bumping to nix unstable colima which is at 0.6.7 seems to fix it
|
I hit the same issue on an M3 mac on Sonoma 14.2.1 with colima version 0.5.6 (it is the current |
|
I encountered the same issue when I ran Colima without installing Docker first. The problem persisted even after I installed Docker or removed everything and reinstalled. However, I was able to resolve it by deleting the cache folder |
|
@royalan for your information, the command |
|
I experienced the same problem on Apple M1 Max chip under Sonoma 14.2.1
|
|
Not subtle, but what worked for me was |
|
I have the same problem, and all of the workarounds mentioned above has failed. I've tried I'm also on Apple M1 Max chip under Sonoma 14.2.1. |
|
Running on a fresh (mirrored, clean) Sonoma 14.3 / Apple M2 Max. Only installed brew, Colima, docker and docker-compose. Took a while to success the ssh config: |
|
I had the same issue on an M1 Max chip on Sonoma 14.3.1. I was able to get colima to work by uninstalling colima, removing the .colima directory and then using the |
solved! thank you!!!! |
|
I struggled with this as well and what ended up working for me are the commands: Running Mac M1 Max on Sonoma 14.4 |
|
Running Mac M2 Max on Ventura 13.6.2 I cleared the cache by running |
|
nothing helps me m2 chips os 14.2.1 |
Description
Colima stuck with
$colima start
$colima status
FATA[0000] colima is not running$which colima
/opt/local/bin/colima$which qemu-img
/opt/local/bin/qemu-img$limactl -v
limactl version 0.19.0$qemu-img --version
$colima version
$qemu-img --version
$colima start --verbose
Version
Operating System
Output of
colima statusReproduction Steps
$colima status
FATA[0000] colima is not runningExpected behaviour
colima should start
Additional context
└─(23:00:39)──> more /Users/admin/.colima/_lima/colima/serial.log
The text was updated successfully, but these errors were encountered: