Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Waiting for essential requirement ssh #215

Closed
david-sauvage opened this issue Mar 11, 2022 · 5 comments
Closed

Waiting for essential requirement ssh #215

david-sauvage opened this issue Mar 11, 2022 · 5 comments

Comments

@david-sauvage
Copy link

david-sauvage commented Mar 11, 2022

Hey there,

I'm facing an issue that seems to be known but can't get thought it.
I've been working with colima to start a few docker container for over 2 months and since yesterday, colima does not start, waiting for ssh.

$ colima start
INFO[0000] using docker runtime                         
INFO[0000] starting colima                              
INFO[0000] starting ...                                  context=vm
> msg="Using the existing instance \"colima\""
> msg="[hostagent] local user \"DAVID\" is not a valid Linux username (must match \"^[a-z_][a-z0-9_-]*$\"); using \"lima\" username instead"
> msg="[hostagent] Starting QEMU (hint: to watch the boot progress, see \"/Users/DAVID/.lima/colima/serial.log\")"
> msg="SSH Local Port: 53756"
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""

Here is the version :
$ colima version colima version 0.3.4 git commit: 5a4a70481ca8d1e794677f22524e3c1b79a9b4ae

Here is the serial log :
serial.log

And seems it may caused by libslirp

$ brew info libslirp
libslirp: stable 4.6.1 (bottled)

Tell me if you need other informations or anything I can do to solve this.

Thank you !

@abiosoft
Copy link
Owner

  • Does it simply get stuck waiting for ssh or it eventually crashes?
  • Can you kindly share the verbose output
    colima start --verbose
    
  • Can you try starting another instance by specifying a profile name.
    colima start second # this starts another instance named 'second'.

@david-sauvage
Copy link
Author

It eventually crashes.

Here is the verbose output (seems close to the normal one) :

$ colima start --verbose
INFO[0000] using docker runtime                         
INFO[0000] starting colima                              
INFO[0000] starting ...                                  context=vm
> msg="Using the existing instance \"colima\""
> msg="[hostagent] local user \"DAVID\" is not a valid Linux username (must match \"^[a-z_][a-z0-9_-]*$\"); using \"lima\" username instead"
> msg="[hostagent] Starting QEMU (hint: to watch the boot progress, see \"/Users/DAVID/.lima/colima/serial.log\")"
> msg="SSH Local Port: 49478"
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="did not receive an event with the \"running\" status"
FATA[0600] error starting vm: error at 'starting': exit status 1 

On the other side using another new profile worked :

$ colima start second
INFO[0000] starting colima [profile=second]             
INFO[0000] creating and starting ...                     context=vm
INFO[0030] provisioning ...                              context=docker
INFO[0030] restarting VM to complete setup ...           context=docker
INFO[0030] stopping ...                                  context=vm
INFO[0036] starting ...                                  context=vm
INFO[0057] starting ...                                  context=docker
INFO[0062] waiting for startup to complete ...           context=docker
INFO[0062] done     

After that I have an empty docker state but it could help me.
Is there anyway to reset the default profile in order to have everything cleaned up ?

Thank you so much for your help 👍

@abiosoft
Copy link
Owner

Is there anyway to reset the default profile in order to have everything cleaned up ?

Yeah, by deleting it via colima delete. You can simply delete and restart the default profile and it should work.
As for deleting other profiles it is colima delete <profile-name> e.g. colima delete second.

@abiosoft
Copy link
Owner

I will be closing this. Feel free to re-open if you are still having the issue.

@david-sauvage
Copy link
Author

Everything is working fine for me now.
Thank you so much !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants