-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
can not find minikube-v1.0.7.iso on windows #1310
Comments
Were you able to fix this? It looks like you might have been having some connectivity issues. |
I appear to be having the same problem:
The file at that location does exist - so I'm wondering why it "cannot find the path specified" |
I had this same issue in PowerShell this morning. Switched to Command Prompt and it went away. |
Unable to reproduce the same issue on PowerShell; |
Hi there, Same error for me even on the Command Prompt.
My Users directory is on a separate partition. Best regards, |
@bleleve you can specify the path for the .minikube directory by setting the MINIKUBE_HOME env variable |
@aaron-prindle It works ! Thank you very much. |
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. |
@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? |
@netroby friendly ping. Were you able to fix this? |
I can not fix this . I am not good at this. |
@netroby It seems that your Users directory is on a separate partition than minikube( |
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. |
Agreeing with @Cryowatt. Why drop the drive letter? On Windows it MUST BE part of the paths. |
@Cryowatt Actually it tries to do as you said, but it fails.
|
Just ran into this on Windows 10. The workaround is to run your Details: On windows the minikube CLI is not appending the drive that minikube is installed on to correctly locate the see output:
|
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. |
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. |
Experienced the same situation on Windows 10 , minikube version v.0.24.1 |
Hi, I got similar problem on Mac:
How can I fix this? |
@kaka89 I had exaclty this problem on windows. Seems like minikube was not able to download the localkube binary without the proxy variables set. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
The only way it worked for me is by following @Strandedpirate comment. thanks a lot ! |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/close
…On Fri, Jun 29, 2018, 10:28 fejta-bot ***@***.***> 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
<#1310 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZuasUO8uxdw2293L3RcrF4YrJGG6ks5uBZDdgaJpZM4MvG7N>
.
|
change current dir to "C:\WINDOWS\system32>" (maybe the disk where iso is) and it starts successfully. |
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). |
@Strandedpirate - it's worse than that :(.
... which is probably why this is such a recurring issue for windows users :). |
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. |
I did this to make it works. I change directory to the given iso directory and launch minikube from there. |
It looks to me like the problem starts with the invalid URL generated by 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. |
Nice step by step guide on how to kill your open source project by refusing to fix defects. |
Thanks @aaron-prindle, setting MINIKUBE_HOME to D:/ worked fine for me |
setting |
@Strandedpirate Thanks a lot !!! |
The text was updated successfully, but these errors were encountered: