Minikube: can not find minikube-v1.0.7.iso on windows

Created on 31 Mar 2017 · 34Comments · Source: kubernetes/minikube

PS D:\Program Files\Docker Toolbox> minikube start
Starting local Kubernetes cluster...
Starting VM...
Downloading Minikube ISO
 89.26 MB / 89.26 MB [==============================================] 100.00% 0s
E0331 09:11:49.439984    2344 start.go:113] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/huzhifeng/.minikube/cache/iso/minikube-v1.0.7.iso: The system cannot find the path specified..

 Retrying.
E0331 09:11:49.442930    2344 start.go:119] Error starting host:  Error creating host: Error creating machine: Error in driver during machine creation: open /Users/huzhifeng/.minikube/cache/iso/minikube-v1.0.7.iso: The system cannot find the path specified.
================================================================================
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
================================================================================
Please enter your response [Y/n]:
Y
E0331 09:12:41.895005    2344 util.go:142] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: dial tcp 216.58.200.234:443: i/o timeout

kinbug lifecyclrotten owindows

Source

29e7e280-0d1c-4bba-98fe-f7cd3ca7500a

Most helpful comment

@bleleve you can specify the path for the .minikube directory by setting the MINIKUBE_HOME env variable
https://github.com/kubernetes/minikube#minikube-environment-variables

aaron-prindle on 6 Apr 2017

👍11 🎉2

All 34 comments

Were you able to fix this? It looks like you might have been having some connectivity issues.

r2d4 on 31 Mar 2017

I appear to be having the same problem:

D:\Dev\Kubernetes\first-test>minikube start --vm-driver=hyperv
Starting local Kubernetes cluster...
Starting VM...
E0401 21:56:12.486990   12748 start.go:113] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/Paul/.minikube/cache/iso/minikube-v1.0.7.iso: The system cannot find the path specified..

 Retrying.
E0401 21:56:12.492994   12748 start.go:119] Error starting host:  Error creating host: Error creating machine: Error in
driver during machine creation: open /Users/Paul/.minikube/cache/iso/minikube-v1.0.7.iso: The system cannot find the path specified.

The file at that location does exist - so I'm wondering why it "cannot find the path specified"

lostpebble on 1 Apr 2017

I had this same issue in PowerShell this morning. Switched to Command Prompt and it went away.

typenil on 2 Apr 2017

👍1

Unable to reproduce the same issue on PowerShell; minikube version: v0.17.1, Win10 (anniversary update)... As mentioned, looks like networking issues.

gbraad on 4 Apr 2017

Hi there,

Same error for me even on the Command Prompt.

c:\Program Files\Kubernetes>minikube start --vm-driver=hyperv
Starting local Kubernetes cluster...
Starting VM...
E0406 18:24:06.365108   10272 start.go:113] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/Benoit/.minikube/cache/iso/minikube-v1.0.7.iso: Le chemin d’accès spécifié est introuvable..

 Retrying.
E0406 18:24:06.366088   10272 start.go:119] Error starting host:  Error creating host: Error creating machine: Error in driver during machine creation: open /Users/Benoit/.minikube/cache/iso/minikube-v1.0.7.iso: Le chemin d’accès spécifié est introuvable.

My Users directory is on a separate partition.

Best regards,
Benoît.

bleleve on 6 Apr 2017

@bleleve you can specify the path for the .minikube directory by setting the MINIKUBE_HOME env variable
https://github.com/kubernetes/minikube#minikube-environment-variables

aaron-prindle on 6 Apr 2017

👍11 🎉2

@aaron-prindle It works ! Thank you very much.

bleleve on 6 Apr 2017

Lets add some documentation that states that you have to either run minikube on your C drive on windows or change the MINIKUBE_HOME env var to point to the drive that minikube is on.

r2d4 on 6 Apr 2017

🎉3

@netroby @lostpebble I believe your issues are related to using a different drive to run minikube vs where .minikube is stored. Can you try specifying the path for the .minikube directory to be accessible by minikube by setting the MINIKUBE_HOME env variable to a directory on the correct drive?

aaron-prindle on 6 Apr 2017

@netroby friendly ping. Were you able to fix this?

aaron-prindle on 12 Apr 2017

I can not fix this . I am not good at this.

29e7e280-0d1c-4bba-98fe-f7cd3ca7500a on 13 Apr 2017

@netroby It seems that your Users directory is on a separate partition than minikube(C:/ vs. D:/)? You will need to set the MINIKUBE_HOME environment variable in your shell to the same drive that the minikube binary is on. So assuming Powershell try:
$env:MINIKUBE_HOME = "D:/"

aaron-prindle on 13 Apr 2017

👍1

This doesn't really make sense as a documentation problem. Minikube should be using the $USERPROFILE environment variable, or $HOMEDRIVE + $HOMEPATH on Windows to determine the path to the user's profile.

Cryowatt on 23 May 2017

👍8

Agreeing with @Cryowatt. Why drop the drive letter? On Windows it MUST BE part of the paths.

ghost on 16 Jun 2017

@Cryowatt Actually it tries to do as you said, but it fails.

ghost on 16 Jun 2017

Just ran into this on Windows 10. The workaround is to run your minikube start command from the same drive that minikube is installed on. e.g. c:\

Details:
This is not an issue with powershell vs cmd. This issue is arising because we are running a shell from a drive that minikube is not installed on. e.g. d:\ or t:\ or whatever.

On windows the minikube CLI is not appending the drive that minikube is installed on to correctly locate the .iso image. It doesn't matter if the MINIKUBE_HOME is set or not; the drive letter is NOT appended.

see output:

t:\git> minikube start --profile=jenkins-test                                                                                                                           minikube start --profile=jenkins-test                                                                                           
Starting local Kubernetes v1.7.0 cluster...                                                                                       
Starting VM...                                                                                                                    
E0825 11:55:45.367940    4820 start.go:129] Error starting host: Error creating host: Error executing step: Creating VM.          
: open /Users/user1/.minikube/cache/iso/minikube-v0.23.0.iso: The system cannot find the path specified..                 

 Retrying.                                                                                                                        
E0825 11:55:45.371441    4820 start.go:135] Error starting host:  Error creating host: Error executing step: Creating VM.         
: open /Users/user1/.minikube/cache/iso/minikube-v0.23.0.iso: The system cannot find the path specified.

Strandedpirate on 25 Aug 2017

👍8 🎉3

I've just looked into this issue. The bug is in docker/machine not in minikube, or actually in the way Go handle file URLs. You can see the issue regarding Go's handling of file paths on Windows, net/url: add test of "Windows" file URL. This "bug" surfaces in mcnutils.goL#199 in docker/machine which in turn causes this bug, as the file URL is not handled correctly on Windows. It is actually the Go URL parser which drops the drive from a file URL.
An example of the URL paser behaviour can be seen here: https://play.golang.org/p/x5kmqDiVL5

kichristensen on 26 Aug 2017

👍1

Couldn't this be properly handled by changing the way the "Boot2DockerURL" config parameter is written when downloading the ISO file? All other parameters on a windows system is written as path strings except the Boot2DockerURL.

Or actually, aborting with an error, or setting it ourselves if the MINIKUBE_HOME path is not set at startup, would lead to users on windows not experiencing this problem at all.

danter on 14 Oct 2017

👍1

Experienced the same situation on Windows 10 , minikube version v.0.24.1
I added MINIKUBE_HOME but did not work, I moved the minikube bin file to the C:/ and it finally worked

LeoQuote on 18 Dec 2017

Hi, I got similar problem on Mac:

Starting local Kubernetes v1.8.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
E1229 10:29:08.616838    9423 start.go:223] Error updating cluster:  Error updating localkube from uri: Error creating localkube asset from url: Error opening file asset: /Users/user007/.minikube/cache/localkube/localkube-v1.8.0: open /Users/user007/.minikube/cache/localkube/localkube-v1.8.0: no such file or directory

How can I fix this?

kaka89 on 29 Dec 2017

@kaka89 I had exaclty this problem on windows.
Since I'm behind a proxy, setting http_proxy and https_proxy environment variables fixed this.

Seems like minikube was not able to download the localkube binary without the proxy variables set.

Addisco on 13 Feb 2018

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.

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

fejta-bot on 14 May 2018

The only way it worked for me is by following @Strandedpirate comment. thanks a lot !

eagleyes on 30 May 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

fejta-bot on 29 Jun 2018

/close

On Fri, Jun 29, 2018, 10:28 fejta-bot notifications@github.com wrote:

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta
https://github.com/fejta.
/lifecycle rotten
/remove-lifecycle stale

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/1310#issuecomment-401228900,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZuasUO8uxdw2293L3RcrF4YrJGG6ks5uBZDdgaJpZM4MvG7N
.

gbraad on 29 Jun 2018

😕1

change current dir to "C:\WINDOWS\system32>" (maybe the disk where iso is) and it starts successfully.

chenmin1992 on 21 Sep 2018

🎉3 👍3

This can't be closed - over a year later it's still an active bug in v0.32 (it's taken me most of an hour to discover that minikube fails if you have multiple drive letters/partitions/etc -- and that it has an incorrect error message (fails to say which hard drive it's accessing)).

OK, sure, the root issue is a bug in Go. But ... at the very least minikube needs to be updated to warn people that it minikube currently has no built-in fix for this bug, with an error message that is accurate (says which hard drive it's accessing!) and advising the user of the alternative options for specifying/overriding the hard drive it uses.

Also, it would be helpful to update the k8s.io website's main guide on minikube, that mentions none of this: https://kubernetes.io/docs/setup/minikube/ (I'll file a bug there on that).

adamgit on 9 Jan 2019

👍1

@Strandedpirate - it's worse than that :(.

I have minikube exe on D:
I have all development tools, projects, data ... on D:
Minikube silently internally dumps its config data in C:, in my Windows user's home directory (Windows has to run off C:, that's not configurable)
I run minikube from the only drive it has ever been downloaded to, or executed on, and it fails. Because internally it's arbitrarily dumping config data onto an unrelated drive (that it should never even have touched)

... which is probably why this is such a recurring issue for windows users :).

adamgit on 9 Jan 2019

NB: setting the env variable, in minikube v0.32, has no effect - Minikube still tries to reference the wrong drive. So it seems the workaround is itself now removed/broken.

adamgit on 9 Jan 2019

I did this to make it works. I change directory to the given iso directory and launch minikube from there.
cd C:\Users\tester.minikube\cache\iso
d:\tools\kubernetesminikube.exe start

ldjoseph on 28 Feb 2019

It looks to me like the problem starts with the invalid URL generated by pkg/util/downloader.go: return "file://" + filepath.ToSlash(isoPath). While linuxy paths start with a slash, Windows ones do not, so the resulting string has two slashes. The biggest takeaway from both Wikipedia and Microsoft is that local files should result in file scheme URLs with three slashes instead of two.

But kichristensen is right that as long as docker/machine's b2d.go just uses the url's Path directly, a valid URL with a drive letter cannot be opened. So passing an invalid one works better sometimes (only when the drive matches). Perhaps docker/machine could update to handle both the invalid (file://) and valid (file:///) URLs, and then minikube could create valid URLs. I've created fileurl with examples of both the creation and consumption logic that I think would help here.