fail to start on win 10 - error reading

[gadieichhorn]

minikube version
minikube version: v0.12.0

minikube start
Starting local Kubernetes cluster...
E1024 19:31:14.996978 12084 start.go:90] Error starting host: Error attempting to cache minikube iso from url: Error copying temp iso file to destination: rename C:\Users\gadei.minikube\cac
he\iso.tmp-minikube-0.7.iso329963535 C:\Users\gadei.minikube\cache\iso\minikube-0.7.iso: The process cannot access the file because it is being used by another process.. Retrying.
E1024 19:31:14.999980 12084 start.go:96] Error starting host: Error attempting to cache minikube iso from url: Error copying temp iso file to destination: rename C:\Users\gadei.minikube\ca
che\iso.tmp-minikube-0.7.iso329963535 C:\Users\gadei.minikube\cache\iso\minikube-0.7.iso: The process cannot access the file because it is being used by another process.

I tried to reboot and delete the temp files under the .minikube location but still same error

[r2d4]

Looks related to #696. Do you have a minikube VM running? Can you try to minikube delete?

[rhuss]

I have the very same issue, even when I removed .minikube completely before. I'm using --vm-driver=virtualbox btw. After this error occured the .minikube can be deleted without problems, so there is no other process locking the .iso then.

[gadieichhorn]

minikube delete
Deleting local Kubernetes cluster...
Errors occurred deleting machine: Error deleting host: minikube: Host does not exist: "minikube"

I also tried this:

minikube start --kubernetes-version="v1.4.0" --vm-driver="virtualbox" --show-libmachine-logs --alsologtostderr

And yes, I can delete the .minikube folder, nothing is holding any processes.

I have latest docker and VirtualBox both running fine.

Do I need to have kubectrl to run minikube?

[ereOn]

I also have the same issue on Windows 10.

Nothing prevents me from deleting the .minikube folder and its content but it doesn't solve the problem. No minikube VM exists in Hyper-V either.

This is puzzling.

That being said, I was able to unblock the situation by renaming the temp iso file to its intended name minikube-0.7.iso. I faced another issue (#754) but this is probably not related.

Could there be a bug in the code that handles renaming of downloaded ISO files that only occurs in Windows 10 ?

[RaeesBhatti]

I faced same issue when I tried to use latest v0.12.0 release but reverting to v0.11.0 seems to have fixed this issue. But like @ereOn I'm also having an issue connecting to minikube IP.

[rhuss]

@jimmidyson I'm not very fluent in Go but could it be that the tempFile must be closed after the copy before the file can be renamed ?

[jimmidyson]

Fixed in #756

[jimmidyson]

@dlorenc @r2d4 Can we get a release out with the fix in #756 as this is affecting Windows users?

[r2d4]

Yeah I think a 0.12.1 makes sense