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

minikube fails to start...minikube vm waiting for login..macOS 10.12.6 VMWareFusion 8.5.8 #1826

Closed
evillgenius75 opened this issue Aug 16, 2017 · 3 comments
Labels
co/vmwarefusion-driver Issues with legacy VMware Fusion Driver kind/bug Categorizes issue or PR as related to a bug.

Comments

@evillgenius75
Copy link

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

Please provide the following details:

Environment:

Minikube version (use minikube version): minikube version: v0.21.0

  • OS (e.g. from /etc/os-release): macOS 10.12.6 (16G29)
  • VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): "DriverName": "vmwarefusion"
  • ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
    "ISO": "/Users/edvilla/.minikube/machines/minikube/boot2docker.iso",
    "Boot2DockerURL": "file:///Users/edvilla/.minikube/cache/iso/minikube-v0.23.0.iso",
    "ConfigDriveISO": "",
  • Install tools:
  • Others:

What happened:
After first install vm boots completely and kubectl is registered and works with no issues. After a successful minikube stop, after trying to start again, the VM will stop at asking for login. The terminal shows as follows:
`➜ minikube start --vm-driver=vmwarefusion
Starting local Kubernetes v1.7.0 cluster...
Starting VM...
E0816 09:00:48.144984 11457 start.go:129] Error starting host: Temporary Error: Error configuring auth on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded.

Retrying.`

What you expected to happen:
minikube vm auto logs in and SSH tunnel is established
How to reproduce it (as minimally and precisely as possible):

Output of minikube logs (if applicable):

Anything else do we need to know:
If I delete the ~/.minikube directory and delete the vm manually from VMware fusion, I can launch again with no issues, just first run.

@r2d4 r2d4 added co/vmwarefusion-driver Issues with legacy VMware Fusion Driver kind/bug Categorizes issue or PR as related to a bug. labels Aug 16, 2017
@cbandy
Copy link

cbandy commented Sep 1, 2017

Related to #1382, maybe?

@joshk0
Copy link

joshk0 commented Sep 15, 2017

Yes, it is almost certainly a duplicate.

@r2d4
Copy link
Contributor

r2d4 commented Sep 15, 2017

closing as a dupe of #1382

@r2d4 r2d4 closed this as completed Sep 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/vmwarefusion-driver Issues with legacy VMware Fusion Driver kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants