-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Hung at "Starting VM", ssh fails with "attempted methods [none publickey], no supported methods remain" #2776
Comments
Same issue on a fresh Ubuntu 18.04 VM. Running on Google Compute Engine with vmx enabled. Starting from a completely fresh VM, issue appears after running these commands:
Minikube then behaves as follows:
[Hangs Here]
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Closing as dupe of #2126 - this seems to be an ssh authentication issue rather than a networking issue. @davidovich mentioned to me that he suspects a data race in https://github.com/docker/machine/blob/6c90ba4d3da9a37ebc15c4c65d61479db075fca5/libmachine/ssh/keys.go#L57 - which apparently does not close files properly. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Please provide the following details:
Environment:
Minikube version (use
minikube version
): v0.25.0cat ~/.minikube/machines/minikube/config.json | grep DriverName
): virtualboxcat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
What happened:
minikube start hangs after
Tried to find the status:
What you expected to happen:
running minikube cluster, valid status
How to reproduce it (as minimally and precisely as possible):
minikube start, status
Output of
minikube logs
(if applicable):Anything else do we need to know:
The text was updated successfully, but these errors were encountered: