Open errakeshpd-hs opened 9 months ago
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:
[hostagent] Waiting for the essential requirement 1 of 4: "ssh"
Head is spinning trying to understand what could be wrong. Pointers?
After timing out, it gives this:
exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/Users/USER/.colima/_lima/colima/ha.stderr.log")
and the tail end of that file:
{"level":"debug","msg":"executing script \"ssh\"","time":"2023-12-06T09:38:54-08:00"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/Users/USER/.colima/_lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=USER -o ControlMaster=auto -o ControlPath=\"/Users/USER/.colima/_lima/colima/ssh.sock\" -o ControlPersist=yes -p 49195 127.0.0.1 -- /bin/bash]","time":"2023-12-06T09:38:54-08:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 49195: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 49195: Connection refused\\r\\n\": exit status 255","time":"2023-12-06T09:38:54-08:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 4: \"ssh\"","time":"2023-12-06T09:39:04-08:00"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2023-12-06T09:39:04-08:00"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/Users/USER/.colima/_lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=USER -o ControlMaster=auto -o ControlPath=\"/Users/USER/.colima/_lima/colima/ssh.sock\" -o ControlPersist=yes -p 49195 127.0.0.1 -- /bin/bash]","time":"2023-12-06T09:39:04-08:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 49195: Connection refused\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"ssh: connect to host 127.0.0.1 port 49195: Connection refused\\r\\n\": exit status 255","time":"2023-12-06T09:39:04-08:00"}
{"level":"warning","msg":"QEMU did not exit in 3m0s, forcibly killing QEMU","time":"2023-12-06T09:39:14-08:00"}
{"error":"signal: killed","level":"info","msg":"QEMU has exited, after killing forcibly","time":"2023-12-06T09:39:14-08:00"}
{"level":"fatal","msg":"signal: killed","time":"2023-12-06T09:39:14-08:00"}
Hi, similar issue here,
[hostagent] Waiting for the essential requirement 1 of 4: "ssh"
Using a M2 Mac Mini, Ventura 13.6.2 (22G320).
After updating today to Colima version 0.6.7
, the issue persists.
Completely removing Colima:
colima delete
colima prune -a
rm -rf ~/.colima
rm -rf ~/.lima
brew remove colima
brew autoremove
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 --vm-type vz
work for you?
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:
hostagent] Waiting for the essential requirement 1 of 2: "ssh"
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 v0.6.5
.
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!
I hit the same issue on an M3 mac on Sonoma 14.2.1 with colima version 0.5.6 (it is the current colima
on nix stable 23.11). Bumping to the latest 0.6.7 (which is found on nixpkgs unstable) resolves this issue for me.
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 $HOME/Library/Caches/lima
. This explains why it successfully installed on a fresh Mac, as mentioned by @feekApp .
@royalan for your information, the command colima prune -a
does already delete all caches in the Users folder, so for me, it was not related to this...
I experienced the same problem on Apple M1 Max chip under Sonoma 14.2.1
colima start --vm-type vz
worked for me, pruning did nothing
Not subtle, but what worked for me was brew uninstall colima
, wiping my ~/.colima directory
and then brew install colima
. ¯\_(ツ)_/¯
I have the same problem, and all of the workarounds mentioned above has failed. I've tried colima delete -f
, colima prune -a
, deleting the ~/.colima
directory, reinstalling, rebooting, colima start --vm-type vz
, but nothing seems to work.
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:
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
...
...
...
// approx. 3 min ....
, running by setting forwardAgent
and sshConfig
to true
....
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 colima start --vm-type vz
command.
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
colima start --vm-type vz
command.
solved! thank you!!!!
I struggled with this as well and what ended up working for me are the commands:
colima delete
colima start --arch x86_64
Running Mac M1 Max on Sonoma 14.4
Running Mac M2 Max on Ventura 13.6.2
Tried running colima start --arch x86_64
but it was stuck forever on the same log line as above:
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
I cleared the cache by running colima prune -a
, but that didn't help the cause.
However, deleting the ~/.colima
directory solved the issue for me. I checked and saw that this dir contains the ssh_config
as well as various other configuration files. Running colima start --arch x86_64
post this re-downloaded the VM image and recreated all the files, so I think that fixed the issue.
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 status
Reproduction Steps
$colima status
FATA[0000] colima is not running
Expected behaviour
colima should start
Additional context
└─(23:00:39)──> more /Users/admin/.colima/_lima/colima/serial.log