Skip to content
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

[NON_C_DRIVE] when run from C:\ but user config is on different drive #4802

Closed
shreyasp91 opened this issue Jul 18, 2019 · 3 comments · Fixed by #5877
Closed

[NON_C_DRIVE] when run from C:\ but user config is on different drive #4802

shreyasp91 opened this issue Jul 18, 2019 · 3 comments · Fixed by #5877
Labels
kind/bug Categorizes issue or PR as related to a bug. os/windows priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. top-10-issues Top 10 support issues
Milestone

Comments

@shreyasp91
Copy link

shreyasp91 commented Jul 18, 2019

Unable to get Minikube start even when I do it from C: Drive

I run the below command and receive the below error

C:\Kubernetes>minikube start

  • minikube v1.2.0 on windows (amd64)
  • Downloading Minikube ISO ...
    129.33 MB / 129.33 MB [============================================] 100.00% 0s
  • Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
    E0718 09:14:58.371558 12332 start.go:559] StartHost: create: creating: open /.minikube/cache/iso/minikube-v1.2.0.iso: The system cannot find the path specified.

X Unable to start VM

  • After some digging in I found the .minikube folder is getting created on the :H network drive, this is my company provided PC, i'm not sure if its has anything to do with permission.
  • when ever I open the windows CMD its start with H: and I navigate to C: and run the command, yet for some reason the .minikube gets created in :H.

image

image

  • I'm new to this, just started to learn K8s, any help on this is deeply appreciated.

Version :- Windows 10

Regards,
Shreyas

@tstromberg
Copy link
Contributor

tstromberg commented Jul 18, 2019

Hey @shreyasp91 - I'm sorry to hear that this is not working correctly on your machine. I think you may have found a situation I wasn't aware of. It's possible to use https://github.com/kubernetes/minikube/blob/master/docs/env_vars.md to set a different location for the minikube configs to be stored. Do you mind trying this for me:

setx MINIKUBE_HOME C:\\Kubernetes\\.minikube

And running minikube <your arguments> --alsologtostderr -v=1

If that doesn't work, try:

setx MINIKUBE_HOME /Kubernetes/.minikube

I imagine other people are running into this, so I would really like to see this get fixed soon. If you don't mind sharing the output of both minikube start --alsologtostderr -v=1 attempts, it would be very helpful.

@tstromberg tstromberg changed the title Minikube start fails on C: on Windows [NON_C_DRIVE] <iso> The system cannot find the path specified (but it's actually being run from C:\!) Jul 18, 2019
@tstromberg tstromberg changed the title [NON_C_DRIVE] <iso> The system cannot find the path specified (but it's actually being run from C:\!) [NON_C_DRIVE] when run from C:\ but user config is on different drive Jul 18, 2019
@tstromberg tstromberg added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/needs-information Indicates an issue needs more information in order to work on it. labels Jul 18, 2019
@shreyasp91
Copy link
Author

Hi @tstromberg ,

Thank you so much, I ran "setx MINIKUBE_HOME C:\Kubernetes\.minikube" and it worked like a charm.

Regards,
Shreyas

minikube install verbose.txt

@tstromberg tstromberg added this to the v1.4.0 Candidate milestone Aug 6, 2019
@tstromberg tstromberg removed this from the v1.4.0 Candidate milestone Aug 19, 2019
@tstromberg tstromberg removed the triage/needs-information Indicates an issue needs more information in order to work on it. label Aug 22, 2019
@tstromberg tstromberg added this to the v1.5.0-candidate milestone Sep 16, 2019
@tstromberg tstromberg added the kind/bug Categorizes issue or PR as related to a bug. label Sep 19, 2019
@tstromberg
Copy link
Contributor

I haven't tried - but as far as I know, this is still an issue in v1.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. os/windows priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. top-10-issues Top 10 support issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants