Minikube: Running `minikube start` followed by 'minikube start' errors on Windows/HyperV

[aaron-prindle]

When attempting to run minikube start followed by minikube start on Windows/HyperV, an error occurs and the VM is left without files being transferred in properly:

Error:
util.go:66: Error running command: start --vm-driver=hyperv --cpus=4 $env:EXTRA_BUILD_ARGS E1109 16:26:52.910586 7736 start.go:115] Error updating cluster: Error updating localkube from asset: Error transferring localkube via ssh: Error running scp command: Process exited with: 1. Reason was: ()

[rodcloutier]

Also present with a VirtualBox driver on Windows 7

[mnuttall]

Seen today on Windows 10, hyperv. Worked around by stopping and deleting the minikube VM in Hyper-V Manager, deleting ~/.minikube and trying again.

[asnowfix]

Still present on Windows 10 with VirtualBox driver. VirtualBox 5.0.32, Minikube 0.17.1

$ minikube start –-logtostderr
Starting local Kubernetes cluster...
Starting VM...
SSH-ing files into VM...
E0317 11:16:27.206221    1428 start.go:140] Error updating cluster:  Error running scp command: Process exited with: 1. Reason was:  ()
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================

[asnowfix]

Confirmed with VirtualBox 5.0.36

Starting local Kubernetes cluster...
Starting VM...
SSH-ing files into VM...
E0317 11:33:55.983350   17004 start.go:140] Error updating cluster:  Error running scp command: Process exited with: 1. Reason was:  ()
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================

[themadarchitect]

This issue is still present in Kubernetes v1.6.3, Minikube 0.17.1 and VirtualBox 5.1.22

[BoasE]

got the some on windows 10 latest updates

[nzeng]

I run "minikube start", error occured: "Moving files into cluster...
E0622 16:57:16.454013 6049 start.go:155] Error updating cluster: Error copying file to target location: invalid argument". but when i run with sudo, no more errors.

[jahantech]

C:\Users\Jahan\Downloads>minikube start
========================================
kubectl could not be found on your path. kubectl is a requirement for using minikube
To install kubectl, please do the following:

download kubectl from:
https://storage.googleapis.com/kubernetes-release/release/v1.6.4/bin/windows/amd64/kubectl.exe
Add kubectl to your system PATH

To disable this message, run the following:

minikube config set WantKubectlDownloadMsg false
========================================
Starting local Kubernetes v1.6.4 cluster...
Starting VM...
Moving files into cluster...
E0622 16:43:13.816314   10504 start.go:155] Error updating cluster:  Error running scp command: Process exited with status 1

Is this a common problem or is it just because of my "cygwin" paths for scp?

[jahantech]

I can confirm that deleting and recreating cluster fixed the issue:

C:\Users\Jahan\Downloads>minikube delete
========================================
kubectl could not be found on your path. kubectl is a requirement for using minikube
To install kubectl, please do the following:

download kubectl from:
https://storage.googleapis.com/kubernetes-release/release/v1.6.4/bin/windows/amd64/kubectl.exe
Add kubectl to your system PATH

To disable this message, run the following:

minikube config set WantKubectlDownloadMsg false
========================================
Deleting local Kubernetes cluster...
Machine deleted.

C:\Users\Jahan\Downloads>minikube start
========================================
kubectl could not be found on your path. kubectl is a requirement for using minikube
To install kubectl, please do the following:

download kubectl from:
https://storage.googleapis.com/kubernetes-release/release/v1.6.4/bin/windows/amd64/kubectl.exe
Add kubectl to your system PATH

To disable this message, run the following:

minikube config set WantKubectlDownloadMsg false
========================================
Starting local Kubernetes v1.6.4 cluster...
Starting VM...
Moving files into cluster...
Setting up certs...
Starting cluster components...
Connecting to cluster...
Setting up kubeconfig...
Kubectl is now configured to use the cluster.

[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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[jahantech]

/close

[zlance]

I'm getting this with minikube 0.28 on ubuntu 17.04 vm, with deleting minikube not cleaning it up.

[kaussandeep]

I get this error on running
sudo minikube start --memory 4096 --vm-driver-none