minikube: vmwarefusion: handshake failed: ssh: unable to authenticate, no supported methods remain

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG REPORT

Please provide the following details:

Environment:

Minikube version (use minikube version):

  • OS: minikube version: v0.23.0
  • VM Driver: vmwarefusion
  • ISO version: file:///Users/kchung/.minikube/cache/iso/minikube-v0.23.6.iso
  • Install tools:
  • Others: The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):

What happened:

Running minikube start --vm-driver=vmwarefusion gets stuck:

~
❯ minikube start --vm-driver=vmwarefusion
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
Downloading Minikube ISO
 140.01 MB / 140.01 MB [============================================] 100.00% 0s
E1027 02:31:16.971076    3294 start.go:150] Error starting host: Error creating host: Error executing step: Provisioning VM.
: Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain.

 Retrying.
E1027 02:31:16.971774    3294 start.go:156] Error starting host:  Error creating host: Error executing step: Provisioning VM.
: Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
	minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:

What you expected to happen:

Using the previous release of minikube makes it further and seems to work better.

~
❯ minikube start --vm-driver=vmwarefusion
There is a newer version of minikube available (v0.23.0).  Download it here:
https://github.com/kubernetes/minikube/releases/tag/v0.23.0

To disable this notification, run the following:
minikube config set WantUpdateNotification false
Starting local Kubernetes v1.7.5 cluster...
Starting VM...
Downloading Minikube ISO
 139.09 MB / 139.09 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.

How to reproduce it (as minimally and precisely as possible):

See above. minikube start --vm-driver=vmwarefusion

Output of minikube logs (if applicable):

~ 8m 51s
❯ minikube logs
F1027 02:33:49.237101    3360 logs.go:50] Error getting cluster bootstrapper: getting localkube bootstrapper: getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

Anything else do we need to know:

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 23 (4 by maintainers)

Most upvoted comments

It looks like the authorized ssh keys are not set up properly for the docker user in the VM. While the handshake failures are logged, I issued the following command in another terminal, and the startup of minikube finished successfully:

"/Applications/VMware Fusion.app/Contents/Library/vmrun" -gu docker -gp tcuser runScriptInGuest /Users/$USER/.minikube/machines/minikube/minikube.vmx /bin/sh "mkdir /home/docker/.ssh; cp /Users/$USER/.minikube/machines/minikube/id_rsa.pub /home/docker/.ssh/authorized_keys; chown -R docker:staff /home/docker/.ssh"

+43
msieper on Nov 2, 2017

Try to run

minikube delete
rm -rf ~/.minikube
minikube start --vm-driver=vmwarefusion

Solved the problem for me

+12
dominikhahn on Oct 30, 2017

This is still happening with v.29 and the chain of “ssh bug during install” issues ends here. If I use the v.27 iso (with the argument --iso-url “https://storage.googleapis.com/minikube/iso/minikube-v0.26.0.iso”) it works, but any of the v.28+ isos stall during install with the recurring “Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [publickey none], no supported methods remain” error. Occasionally the error turns into “Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [publickey none], no supported methods remain” as well, whether I am using the native Go ssh client or the one at https://github.com/PowerShell/Win32-OpenSSH .

+3
mdavidii on Sep 29, 2018

This issue is still happening with the following configuration OSX: 10.13.4 VMWare Fusion: 8.5.10 Minikube: 0.26.0

@msieper’s fix seems to work to a point, but it looks like there may be other problems with the vmware fusion driver.

+3
disrvptor on Apr 20, 2018

Had the same issue. Confirmed @msieper 's solution works. I am not sure since when this is broken, but we need to fix it. It’s hard to fix it in vmwarefusion because it locates in docker/machine where they are basically inactive. I will make sure when #2118 gets merged, it doesn’t have this issue.

+2
anfernee on Nov 8, 2017

This issue has been fixed in v0.25.0.

+1
anfernee on Jan 26, 2018

Yeah, I ran this while doing a minikube start

 while true; do "/Applications/VMware Fusion.app/Contents/Library/vmrun" -gu docker -gp tcuser runScriptInGuest /Users/$USER/.minikube/machines/minikube/minikube.vmx /bin/sh "mkdir /home/docker/.ssh; cp /Users/$USER/.minikube/machines/minikube/id_rsa.pub /home/docker/.ssh/authorized_keys; chown -R docker:staff /home/docker/.ssh"; sleep 5; done
+1
zoidyzoidzoid on Jan 12, 2018
Read more comments on GitHub
← minikube: vmwarefusion: failed to start after stop: Error configuring auth on host: Too many retries waiting for SSH to be available
minikube: vmware+vbox: kubelet: dial tcp 192.168.99.100:8443: getsockopt: connection refused →