Closed
Description
Environment:
minikube version: v1.0.0
OS: Ubuntu 16.04 LTS (Xenial Xerus)
VM Driver: none
What happened: ```
Created a VM with none driver, stopped it, then started it again. The VM failed to start and minikube reported that it crashed.
What I expected to happen:
the VM created by the first minikube start command is started.
Output from the second minikube start command:
😄 minikube v1.0.0 on linux (amd64)
🤹 Downloading Kubernetes v1.14.0 images in the background ...
💡 Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🔄 Restarting existing none VM for "minikube" ...
⌛ Waiting for SSH access ...
💣 Unable to start VM: detecting provisioner: Too many retries waiting for SSH to be available. Last error: Maximum number of
retries (60) exceeded
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new
Output from 'sudo minikube start --alsologtostderr -v=8 --vm-driver=none':
⌛ Waiting for SSH access ...
Waiting for SSH to be available...
Getting to WaitForSSH function...
Error getting ssh command 'exit 0' : driver does not support ssh commands
To reproduce:
sudo minikube start --vm-driver=none
sudo minikube stop
sudo minikube start --vm-driver=none
Starting a stopped VM was working in minikube v0.28.