minikube: Error Provisioning VM: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

Environment:

Minikube version: v0.28.0

OS : Windows 10
VM Driver: hyperv

What happened: Starting minikube with v0.28.0 throws the following error:

E0614 17:09:30.577303 1732 start.go:174] 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 [publickey none], 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

What you expected to happen: minikube to start correctly

How to reproduce it (as minimally and precisely as possible): minikube start --vm-driver hyperv --hyperv-virtual-switch “Primary Virtual Switch” --cpus 3 --memory 4096

Output of minikube logs (if applicable): F0614 17:18:44.984795 16020 logs.go:50] Error getting cluster bootstrapper: getting kubeadm 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:

I have tried the latest version on two different computers running different versions of Windows 10 and both get the same issue. If I downgrade to v0.27.0 then it starts up fine.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 9
Comments: 16 (2 by maintainers)

Most upvoted comments

I can also confirm. Had the same error with ssh handshake on Windows 10 Pro 1803 (OS build 17134.228) with Hyper-V

Command used: minikube start --vm-driver="hyperv" --memory=4096 --cpus=4 --hyperv-virtual-switch="External" --v=7 --alsologtostderr Initial version: 0.28.2 Tried the following (removed .minikube and .kube between the steps):

remove optional windows openssh -> didn’t work install openssh via chocolate -> didn’t work Downgrading to version 0.27 using the built in ssh go iplmenetation -> didn’t work Downgrading to 0.27 using the optional windows openssh -> didn’t work Downgrading to 0.27 using the OpenSSH 7.7.2.1 from chocolatey --> THIS WORKED!

Seems like there is serious bug in 0.28 version.

stefanjarina on Sep 1, 2018

@srflaxu40 I downgraded to 0.27.0 to get it working in the meantime.

F21 on Jun 29, 2018

My issue was fixed by upgrading to the latest version of Virtual Box and removing ~/.minikube, then running minikube start.

ch-abrandt on Jun 14, 2018

I found that I can start minikube with 0.28.2 but I need to tinker with various settings and try a couple of times to get it working.

I need to run it from the same drive as my user profile (C:)
I found that if I set the memory to 4096, it fails more often than if I set it to something lower
When I start it, I keep an eye on the VM from the hyperv manager, and if I ever see the memory jump from what I set it to (like 4096) to something lower (like 796), I can confidently say it will fail so I stop it, delete it, and try again. Sometimes it works the next time. Closing programs seems to help (even though I’m nowhere near max RAM usage)
If I move networks (switching from Wi-Fi to Ethernet for example), my connection to the cluster breaks - so I need to delete and recreate my cluster whenever I switch (or my comp goes to sleep) - this is less relevant for starting, but I get the ssh handshake fail on an existing cluster when this happens

m1o1 on Sep 1, 2018

Yep, downgrade to 0.27 works for me as well.

ducminhn on Aug 30, 2018