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

[User name: admin] Waiting for the essential requirement 1 of 4: "ssh" #2117

Closed
fortunateLeopard opened this issue Jan 8, 2024 · 9 comments · Fixed by #2827
Closed

[User name: admin] Waiting for the essential requirement 1 of 4: "ssh" #2117

fortunateLeopard opened this issue Jan 8, 2024 · 9 comments · Fixed by #2827
Labels
duplicate This issue or pull request already exists

Comments

@fortunateLeopard
Copy link

fortunateLeopard commented Jan 8, 2024

Description

I can't get seem to connect via ssh to lima with default using either drivers, output for vz below. My local username is admin in case that's relevant.

limactl --version    
limactl version 0.19.1

% sw_vers
ProductName:		macOS
ProductVersion:		14.2.1
BuildVersion:		23C71
limactl start             
INFO[0000] Using the existing instance "default"        
INFO[0000] Starting the instance "default" with VM driver "vz" 
INFO[0000] [hostagent] hostagent socket created at /Users/admin/.lima/default/ha.sock 
INFO[0000] [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/admin/.lima/default/serial*.log") 
INFO[0000] [hostagent] new connection from  to          
INFO[0001] SSH Local Port: 60022                        
INFO[0001] [hostagent] Waiting for the essential requirement 1 of 2: "ssh" 
INFO[0001] [hostagent] [VZ] - vm state change: running  
INFO[0011] [hostagent] Waiting for the essential requirement 1 of 2: "ssh" 
INFO[0021] [hostagent] Waiting for the essential requirement 1 of 2: "ssh" 
...
{"level":"info","msg":"Waiting for the essential requirement 1 of 2: \"ssh\"","time":"2024-01-08T06:40:33-05:00"}
{"level":"debug","msg":"executing script \"ssh\"","time":"2024-01-08T06:40:33-05:00"}
{"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/Users/admin/.lima/_config/user\" -o IdentityFile=\"/Users/admin/.ssh/aviculturist\" -o IdentityFile=\"/Users/admin/.ssh/id_bitnym\" -o IdentityFile=\"/Users/admin/.ssh/id_ed25519_moscoviumalchemist\" -o IdentityFile=\"/Users/admin/.ssh/lucr\" -o IdentityFile=\"/Users/admin/.ssh/pickwp_id_rsa\" -o IdentityFile=\"/Users/admin/.ssh/sozot_github_id_rsa\" -o IdentityFile=\"/Users/admin/.ssh/wpspring_github_id_rsa\" -o IdentityFile=\"/Users/admin/.ssh/wpsy_bitbucket_id_rsa\" -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=admin -o ControlMaster=auto -o ControlPath=\"/Users/admin/.lima/default/ssh.sock\" -o ControlPersist=yes -p 60022 127.0.0.1 -- /bin/bash]","time":"2024-01-08T06:40:33-05:00"}
{"level":"debug","msg":"stdout=\"\", stderr=\"Received disconnect from 127.0.0.1 port 60022:2: Too many authentication failures\\r\\nDisconnected from 127.0.0.1 port 60022\\r\\n\", err=failed to execute script \"ssh\": stdout=\"\", stderr=\"Received disconnect from 127.0.0.1 port 60022:2: Too many authentication failures\\r\\nDisconnected from 127.0.0.1 port 60022\\r\\n\": exit status 255","time":"2024-01-08T06:40:33-05:00"}
@AkihiroSuda AkihiroSuda changed the title Waiting for the essential requirement 1 of 4: "ssh" [User name: admin] Waiting for the essential requirement 1 of 4: "ssh" Jan 8, 2024
@AkihiroSuda
Copy link
Member

My local username is admin in case that's relevant.

Yes, very likely to be relevant

As a workaround, limactl start template://fedora may work

@AkihiroSuda AkihiroSuda added the duplicate This issue or pull request already exists label Jan 8, 2024
@Asutu
Copy link

Asutu commented Jan 15, 2024

I was having the same problem with the "AlmaLinux-9" template, but the problem persisted with "Fedora" as well.

$ limactl start --name default --disk 30 template://fedora
? Creating an instance "default" Proceed with the current configuration
INFO[0001] Starting the instance "default" with VM driver "qemu"
INFO[0001] QEMU binary "/opt/local/bin/qemu-system-x86_64" seems properly signed with the "com.apple.security.hypervisor" entitlement
INFO[0001] Attempting to download the image              arch=x86_64 digest="sha256:ab5be5058c5c839528a7d6373934e0ce5ad6c8f80bd71ed3390032027da52f37" location="https://download.fedoraproject.org/pub/fedora/linux/releases/39/Cloud/x86_64/images/Fedora-Cloud-Base-39-1.5.x86_64.qcow2"
Downloading the image (Fedora-Cloud-Base-39-1.5.x86_64.qcow2)
519.38 MiB / 519.38 MiB [----------------------------------] 100.00% 54.98 MiB/s
INFO[0011] Downloaded the image from "https://download.fedoraproject.org/pub/fedora/linux/releases/39/Cloud/x86_64/images/Fedora-Cloud-Base-39-1.5.x86_64.qcow2"
INFO[0011] Attempting to download the nerdctl archive    arch=x86_64 digest="sha256:5ea4524ff346000bb32ef1d9fb8c4b8e809fbff69260d179218d7c308cc2aa99" location="https://github.com/containerd/nerdctl/releases/download/v1.7.2/nerdctl-full-1.7.2-linux-amd64.tar.gz"
INFO[0011] Using cache "/Users/foobar/Library/Caches/lima/download/by-url-sha256/cd4d072fa7339ae8dbd52bbe23d415242e43648343bd44487fb529e92ccc550e/data"
INFO[0015] [hostagent] hostagent socket created at /Users/foobar/.lima/default/ha.sock
INFO[0015] [hostagent] Using system firmware ("/opt/local/share/qemu/edk2-x86_64-code.fd")
INFO[0015] [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/foobar/.lima/default/serial*.log")
INFO[0015] SSH Local Port: 60022
INFO[0015] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0103] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0191] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0279] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0366] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0454] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0542] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
FATA[0611] did not receive an event with the "running" status
$ limactl --version
limactl version 0.19.1

$ sw_vers
ProductName:	macOS
ProductVersion:	12.7.2
BuildVersion:	21G1974

@timurguseynov
Copy link

timurguseynov commented Feb 12, 2024

I had a similar problem, no logs, no response and it turned out that the machine wasn't starting with UEFI firmware enabled.

Setting firmware legacyBIOS to true worked.

firmware:
  legacyBIOS: true

@AkihiroSuda
Copy link
Member

I had a similar problem, no logs, no response and it turned out that the machine wasn't starting with UEFI firmware enabled.

Doesn't seem relevant to the OP ("My local username is admin")

@timurguseynov
Copy link

timurguseynov commented Feb 12, 2024

I saw switching to fedora didn't work for @Asutu, maybe this will work. Probably need a new issue for that

@wq9578
Copy link

wq9578 commented May 1, 2024

I'm facing the same problem:

% brew install lima
...

% limactl start --plain
INFO[0123] [hostagent] Waiting for the essential requirement 1 of 1: "ssh" 
INFO[0139] [hostagent] Waiting for the essential requirement 1 of 1: "ssh" 
INFO[0150] [hostagent] Waiting for the essential requirement 1 of 1: "ssh" 
...

% limactl start
INFO[0000] [hostagent] Waiting for the essential requirement 1 of 4: "ssh" 
INFO[0017] [hostagent] Waiting for the essential requirement 1 of 4: "ssh" 
INFO[0027] [hostagent] Waiting for the essential requirement 1 of 4: "ssh" 
...

% sw_vers 
ProductName:		macOS
ProductVersion:		14.4.1
BuildVersion:		23E224

% limactl --version
limactl version 0.21.0

Apple M1 chip.

Using the setting

firmware:
  legacyBIOS: true

as suggested above didn't help.

A similar problem on macOS with M1 chip was reported at Colima: abiosoft/colima#690

Maybe related: #255

@bo17age
Copy link

bo17age commented May 30, 2024

I'm working on this

@RyanKlann
Copy link

Same issue here for me.
My local username is admin and its causing me exactly the same issues.

@bo17age
Copy link

bo17age commented Sep 10, 2024

Hi @AkihiroSuda , can you help to review this pull request
#2378

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants