minikube start asking for an ssh password

[arun-gupta]

Using:

• minikube 0.18.0
• Version 5.1.22 r115126 (Qt5.6.2)
• kuibectl v1.6.2
• Platform: darwin/amd64

Starting up minikube cluster using minikube start is asking for password. The sudo password is not working.

What is wrong?

[r2d4]

You shouldn't be prompted for any password, minikube doesn't require root and should be run as your normal user. Can you give any more information? Maybe the ownership of the minikube binary?

[arun-gupta]

Binary is owned by the current user.

0.17.1 starts up successfully with the following output:

0.17.1 $ ./minikube start
There is a newer version of minikube available (v0.18.0).  Download it here:
https://github.com/kubernetes/minikube/releases/tag/v0.18.0

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

[arun-gupta]

Weird, starting a cluster using 0.17.1 and now starting using 0.18.0 seems to work. Not sure what got updated/fixed during the process.

[QuinnyPig]

I'm betting it's an ssh key failure into the VM.

[arun-gupta]

There was no error message indicating that though, but glad it worked at least.

[r2d4]

@QuinnyPig is correct. This happens when the minikube VM is in a bad state (configuration exists but machine and ssh key don't exist).

Going to reopen this, so that we remove this prompt even in bad states.

[tz70s]

Hi @r2d4,
I'm curious about so what is the appropriate result do you expect if we get the ssh key lost?
Thanks!

[r2d4]

We should disable password prompts through an option on the client - so that there is never a password prompt when ssh key authentication fails

[vishwanath79]

hi,

New user here. I'm seeing the same issue. Is there a solve for this? - thanks.

minikube version: v0.20.1
Environment: Mac OS Sierra 10.12.5

I was following the install instructions here: https://github.com/kubernetes/minikube

What happened:
It does not accept root password. Not sure how to get past this. Tried reinstalling as well.

`==> Linking Binary 'minikube-darwin-amd64' to '/usr/local/bin/minikube'.

🍺 minikube was successfully installed!

$ minikube start

Starting local Kubernetes v1.6.4 cluster...

Starting VM...

Password:`

[ghost]

@vishwanath79
I solved similar thing with a solution I found at another github issue somewhere

minikube delete
minikube start

which I guess clears ~/.minikube/machines

[vishwanath79]

@divbit thanks for chiming in. Had tried that as well but that did not work for me either. I gave up on minikube. It was easier for me to just set up a Kubernetes cluster :).

[ghost]

@vishwanath79 No problem, I spent a couple of hours getting it working this morning, so figured to not waste the work just on myself as I came across this thread a couple times.

[songokudbz]

Any news on this? I have minikube version 0.23.0 on Windows and trying to start it with Hyperv. It still waits for you to login to minikube ....

[pienaarp]

I entered 'root' as the root passwords when the VM boots and it works:

Starting local Kubernetes v1.7.5 cluster...
Starting VM...
* ENTER password in VM **
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.

[emoulder]

I was having same issues but the minikube delete seems to have cleared up the problem.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[yujiangshui]

The issue still has.

[imroc]

The issue still has.

[drkrishnan8109]

The issue still exists

[drkrishnan8109]

I tried with username: root, pwd: root and it works. But you may have to think if you need root access. Its just an initial work around, I hope you could change pwds later

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sadjadtalakoob74]

I entered 'root' as the root passwords when the VM boots and it works:

Starting local Kubernetes v1.7.5 cluster...
Starting VM...
* ENTER password in VM **
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.

i have same problem but it works as type "root" for password, thanks

[afbjorklund]

This ticket (and your kubernetes version) is ancient...
Can you try again with the latest, and open a new issue ?

[emoulder]

Sure, thanks.