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

Minikube failing to find ISO on Windows 10 Pro machine using MINIKUBE_HOME #2564

Closed
gsoper78 opened this Issue Feb 22, 2018 · 7 comments

Comments

Projects
None yet
8 participants
@gsoper78

gsoper78 commented Feb 22, 2018

Bug report

Environment: Windows 10 Pro

Minikube version: v1.6.0

  • OS:
  • VM Driver: HyperV
  • ISO version: minikube-v0.25.1.iso
  • Install tools:
  • Others:

What happened:
Tried to start Minikube for the first time. I have a small %HOMEDRIVE% (Corporate network reasons) so used "MINIKUBE_HOME=C:\Minikube" in my user variables to use somewhere without space constraints. Following error is the result:

Starting local Kubernetes v1.6.0 cluster...
Starting VM...
Downloading Minikube ISO
 142.22 MB / 142.22 MB [============================================] 100.00% 0s
E0221 17:04:57.911705    8116 start.go:159] Error starting host: Error creating host: Error executing step: Creating VM.
: open /Minikube/.minikube/cache/iso/minikube-v0.25.1.iso: The system cannot find the file specified..

 Retrying.
E0221 17:04:57.925698    8116 start.go:165] Error starting host:  Error creating host: Error executing step: Creating VM.
: open /Minikube/.minikube/cache/iso/minikube-v0.25.1.iso: The system cannot find the file specified.

"C:\Minikube.minikube\cache\iso\minikube-v0.25.1.iso" is present and opens in Window as if it were a CD so I assume it's in a good state. Lack of "C:" in path in error raises suspicion but may be a red herring.

What you expected to happen:
Minikube to start

How to reproduce it (as minimally and precisely as possible):
Set "MINIKUBE_HOME=C:\Minikube" in the user variables of a Windows 10 Pro machine.

Output of minikube logs (if applicable):
Log folder empty

Anything else do we need to know:

@rprouse

This comment has been minimized.

rprouse commented Feb 22, 2018

Duplicate of #1574? Where is minikube installed? I got the same when running from my D drive, switching to my C drive helped.

@DanielRamosAcosta

This comment has been minimized.

DanielRamosAcosta commented Mar 1, 2018

As @rprouse says, I was launching "minikube start" from my D drive, but when launching it from C it works... 😕

@aaron-prindle

This comment has been minimized.

Contributor

aaron-prindle commented Mar 1, 2018

@r2d4 r2d4 added the os/windows label Mar 5, 2018

@davidovich

This comment has been minimized.

Contributor

davidovich commented Mar 30, 2018

Lack of "C:" in path in error raises suspicion but may be a red herring.

I think prepending the drive letter would fix this, and "launch minikube from the drive where it is installed" issues that people are having. But preliminary research into the code (in docker/machine/drivers) does not point to anywhere where the drive is dropped.

minikube depends on client-go from kubernetes and this resolves the default minikube path in this order:

  1. HOME
  2. concatenation of HOMEDRIVE and HOMEPATH
  3. USERPROFILE

This would account for different behaviors reported (if you are not using MINIKUBE_HOME, and you have a HOMEDRIVE and combinations etc.)

But this is only at the minikube level. Drivers make their own asumptions on the HOME drive.

@fejta-bot

This comment has been minimized.

fejta-bot commented Jun 28, 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

This comment has been minimized.

fejta-bot commented Jul 28, 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

@fejta-bot

This comment has been minimized.

fejta-bot commented Aug 27, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment