start fails when run from non-C:\ drive: open minikube.iso: The system cannot find the path specified. #1574

mevam · 2017-06-11T04:32:08Z

minikube start --vm-driver=virtualbox
Starting local Kubernetes v1.6.4 cluster...
Starting VM...
Downloading Minikube ISO
89.51 MB / 89.51 MB 100.00% 0ss
E0611 12:27:47.593274 8356 start.go:127] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/navy/.minikube/cache/iso/minikube-v0.18.0.iso: The system cannot find the path specified..

Retrying.
E0611 12:27:47.608522 8356 start.go:133] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/navy/.minikube/cache/iso/minikube-v0.18.0.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

go version
go version go1.8.2 windows/amd64

Run minikube failed on win 8.1. what should I do？Thanks.

mevam · 2017-06-11T04:40:04Z

minikube start --v=3
Starting local Kubernetes v1.6.4 cluster...
Starting VM...
E0611 12:40:23.765630 4284 start.go:127] Error starting host: Error getting s tate for host: machine does not exist.

Retrying.
E0611 12:40:23.765630 4284 start.go:133] Error starting host: Error getting state for host: machine does not exist

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

minikube start --v=7
Starting local Kubernetes v1.6.4 cluster...
Starting VM...
Found binary path at D:\Sware\minikube\minikube.exe
Launching plugin server for driver virtualbox
Plugin server listening at address 127.0.0.1:16672
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minikube) Calling .GetState
(minikube) DBG | COMMAND: D:\Sware\VirtualBox\VBoxManage.exe showvminfo minikube --machinereadable
(minikube) DBG | STDOUT:
(minikube) DBG | {
(minikube) DBG | }
(minikube) DBG | STDERR:
(minikube) DBG | {
(minikube) DBG | VBoxManage.exe: error: Could not find a registered machine name d 'minikube'
(minikube) DBG | VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0 x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
(minikube) DBG | VBoxManage.exe: error: Context: "FindMachine(Bstr(VMNameOrUuid) .raw(), machine.asOutParam())" at line 2781 of file VBoxManageInfo.cpp
(minikube) DBG | }
E0611 12:40:36.420957 9060 start.go:127] Error starting host: Error getting s tate for host: machine does not exist.

Retrying.
E0611 12:40:36.428003 9060 start.go:133] Error starting host: Error getting state for host: machine does not exist

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

aaron-prindle · 2017-06-12T15:28:42Z

I believe this issue is related to using a D: drive on windows as Minikube is by default stored on the C: drive. Can you try running minikube with the MINIKUBE_HOME env var set to path on the D: drive? For more information see #1310 as setting this should fix it: #1310 (comment)

r2d4 · 2017-06-15T17:38:42Z

ping @mevam

We should add some documentation about this to our main windows docs

ghost · 2017-06-16T10:02:41Z

@r2d4 I don't think it is documentation problem, it is bug. Please see #1310 (comment)

alastairs · 2017-07-26T09:47:43Z

I ran into this same issue, with both minikube and my user profile on C:. I tried setting MINIKUBE_HOME as per @aaron-prindle's comment. I eventually pinned it down to the fact that my pwd was on D: - a simple cd C:\ allowed minikube start to operate correctly.

This has to be a bug @r2d4 - different behaviour depending on your pwd's drive isn't solely a documentation issue.

kylos101 · 2017-11-26T02:21:49Z

@alastairs this saved me from pulling out my remaining hair - thank you!

kylos101 · 2017-11-26T02:34:49Z

@r2d4 Hi there, thank you so much for helping maintain Minikube! I am new to kubernetes, and Minikube is frickin' great.

I wasn't able to run minikube until I CD'd to my C drive (kudos again to @alastairs) - chocolatey installed Minikube to my C drive. I work in F.

Can this issue be changed from a kind/documentation to some type of software change? Or should we create a new request? I am just looking to save future people the trouble, if possible.

fejta-bot · 2018-02-26T19:00:49Z

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

rmorrise · 2018-03-28T13:53:09Z

/remove-lifecycle stale

rmorrise · 2018-03-28T13:53:59Z

This is a bug in how the ISO file path is generated. The drive letter needs to be included in the path.

pxlphile · 2018-05-15T11:12:06Z

Hi all,
I can confirm this behavior (which almost drove me crazy until I found this issue). I run Minikube on a Windows 7 machine, and due to HDD space considerations I've set MINIKUBE_HOME to D:\\minikube.

Yes, double backslashes. The installation is a couple of months old and I don't remember why I had to put it this way. Anyhow, a change to D:\ (among a desperate iteration of minikube delete and minikube profile deletions) got it running for me.

fejta-bot · 2018-08-13T11:16:22Z

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

rmorrise · 2018-08-13T14:09:28Z

/remove-lifecycle stale

fejta-bot · 2018-12-18T22:51:23Z

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 · 2019-01-17T23:36:08Z

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

- On Windows, `minikube` passes in a file URL like `"file://C:/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`, however, due to the way that Go parses URLs, the `"C:"` part is actually parsed as the hostname portion instead of staying at the beginning of the path (golang/go#6027). If `minikube` is run with a working directory on a different drive from where its cache directory resides, it will fail since `libmachine` is only looking at the path portion (in this case: `"/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`) so it fails to find the file (kubernetes/minikube#1574).

douglaswth · 2019-07-23T01:39:19Z

I have a fix for this in docker/machine#4734 that at least works, but I am not quite sure if it is the best approach.

- On Windows, `minikube` passes in a file URL like `"file://C:/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`, however, due to the way that Go parses URLs, the `"C:"` part is actually parsed as the hostname portion instead of staying at the beginning of the path (golang/go#6027). If `minikube` is run with a working directory on a different drive from where its cache directory resides, it will fail since `libmachine` is only looking at the path portion (in this case: `"/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`) so it fails to find the file (kubernetes/minikube#1574). Signed-off-by: Douglas Thrift <dthrift@flexera.com>

tstromberg · 2019-08-27T23:01:15Z

@douglaswth - Nice work! Anything I can do to help move the PR forward?

douglaswth · 2019-10-21T17:58:49Z

@tstromberg Oh! Haven't looked at this in a while, but another coworker was running into this issue so it's back on my radar. If you know of any way to poke the maintainers of docker/machine that might be helpful.

tstromberg · 2019-10-22T18:57:55Z

@douglaswth - Do you mind proposing the PR to https://github.com/machine-drivers/machine in parallel? It's the fork of docker/machine that minikube uses, since docker/machine is mostly dead. Once it's in machine-drivers/machine, we can release a new minikube based on the PR while we wait for the docker/machine upstream to get around to merging things.

@afbjorklund and @gbraad have approval rights on machine-drivers/machine, so we should be able to make progress there. Let me know once the PR is done so that we can poke the right people.

tstromberg · 2019-10-22T19:01:23Z

/cc @blueelvis and @sharifelgamal (our Windows leads) for visibility

- On Windows, `minikube` passes in a file URL like `"file://C:/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`, however, due to the way that Go parses URLs, the `"C:"` part is actually parsed as the hostname portion instead of staying at the beginning of the path (golang/go#6027). If `minikube` is run with a working directory on a different drive from where its cache directory resides, it will fail since `libmachine` is only looking at the path portion (in this case: `"/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`) so it fails to find the file (kubernetes/minikube#1574). Signed-off-by: Douglas Thrift <dthrift@flexera.com> (cherry picked from commit ade5501)

douglaswth · 2019-10-22T21:08:12Z

@tstromberg Okay, I've made machine-drivers/machine#22 for that.

tstromberg · 2019-12-16T22:17:40Z

I believe this was fixed in minikube v1.6: can someone please confirm on Windows?

spdfnet · 2019-12-16T22:26:15Z

I can confirm it working :)

douglaswth · 2019-12-16T22:39:55Z

@tstromberg Woohoo! It's working for me as well!

fejta-bot · 2020-03-15T23:31:29Z

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 · 2020-04-15T00:14:22Z

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

- On Windows, `minikube` passes in a file URL like `"file://C:/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`, however, due to the way that Go parses URLs, the `"C:"` part is actually parsed as the hostname portion instead of staying at the beginning of the path (golang/go#6027). If `minikube` is run with a working directory on a different drive from where its cache directory resides, it will fail since `libmachine` is only looking at the path portion (in this case: `"/Users/douglas/.minikube/cache/iso/minikube-v1.2.0.iso"`) so it fails to find the file (kubernetes/minikube#1574). Signed-off-by: Douglas Thrift <dthrift@flexera.com> (cherry picked from commit ade55018264a1cde51c0c77bed184a0d528759f9)

aaron-prindle added kind/bug Categorizes issue or PR as related to a bug. os/windows labels Jun 11, 2017

r2d4 added kind/documentation Categorizes issue or PR as related to documentation. and removed kind/bug Categorizes issue or PR as related to a bug. labels Jun 15, 2017

r2d4 added kind/bug Categorizes issue or PR as related to a bug. and removed kind/documentation Categorizes issue or PR as related to documentation. labels Nov 28, 2017

udoheld mentioned this issue Feb 1, 2018

Windows 10 minikube doesn't start when installed on different drive #2495

Closed

rprouse mentioned this issue Feb 22, 2018

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

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 26, 2018

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 28, 2018

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 13, 2018

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 13, 2018

tstromberg changed the title ~~Run minikube failed on Windows~~ When run from non-C: drive: open minikube.iso: The system cannot find the path specified. Sep 19, 2018

afbjorklund mentioned this issue Sep 30, 2018

minikube looks for minikube.iso in wrong path #3181

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2018

tstromberg added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 12, 2019

shreyasp91 mentioned this issue Jul 18, 2019

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

Closed

douglaswth mentioned this issue Jul 23, 2019

Fix Windows minikube ISO download docker/machine#4734

Open

AshwinDora mentioned this issue Aug 3, 2019

windows 10 - minikube start error - StartHost: create: creating: open /cache/iso/minikube-v1.2.0.iso: The system cannot find the path specified #4974

Closed

tstromberg added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 20, 2019

TristansCloud mentioned this issue Oct 1, 2019

stop fails: "yaml: control characters are not allowed" + garbage text #5513

Closed

mittman mentioned this issue Oct 6, 2019

minikube stop: Error decoding config from data: ELF #5552

Closed

douglaswth mentioned this issue Oct 22, 2019

Fix Windows minikube ISO download machine-drivers/machine#22

Merged

tstromberg removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. r/2019q2 Issue was last reviewed 2019q2 labels Dec 16, 2019

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2020

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 15, 2020

tstromberg closed this as completed Apr 20, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

start fails when run from non-C:\ drive: open minikube.iso: The system cannot find the path specified. #1574

start fails when run from non-C:\ drive: open minikube.iso: The system cannot find the path specified. #1574

mevam commented Jun 11, 2017 •

edited

Loading

mevam commented Jun 11, 2017 •

edited

Loading

aaron-prindle commented Jun 12, 2017

r2d4 commented Jun 15, 2017

ghost commented Jun 16, 2017 •

edited by ghost

Loading

alastairs commented Jul 26, 2017

kylos101 commented Nov 26, 2017

kylos101 commented Nov 26, 2017

fejta-bot commented Feb 26, 2018

rmorrise commented Mar 28, 2018

rmorrise commented Mar 28, 2018

pxlphile commented May 15, 2018

fejta-bot commented Aug 13, 2018

rmorrise commented Aug 13, 2018

fejta-bot commented Dec 18, 2018

fejta-bot commented Jan 17, 2019

douglaswth commented Jul 23, 2019

tstromberg commented Aug 27, 2019

douglaswth commented Oct 21, 2019

tstromberg commented Oct 22, 2019 •

edited

Loading

tstromberg commented Oct 22, 2019

douglaswth commented Oct 22, 2019

tstromberg commented Dec 16, 2019

spdfnet commented Dec 16, 2019

douglaswth commented Dec 16, 2019

fejta-bot commented Mar 15, 2020

fejta-bot commented Apr 15, 2020

start fails when run from non-C:\ drive: open minikube.iso: The system cannot find the path specified. #1574

start fails when run from non-C:\ drive: open minikube.iso: The system cannot find the path specified. #1574

Comments

mevam commented Jun 11, 2017 • edited Loading

Retrying. E0611 12:27:47.608522 8356 start.go:133] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/navy/.minikube/cache/iso/minikube-v0.18.0.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

mevam commented Jun 11, 2017 • edited Loading

Retrying. E0611 12:40:23.765630 4284 start.go:133] Error starting host: Error getting state for host: machine does not exist

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

Retrying. E0611 12:40:36.428003 9060 start.go:133] Error starting host: Error getting state for host: machine does not exist

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

aaron-prindle commented Jun 12, 2017

r2d4 commented Jun 15, 2017

ghost commented Jun 16, 2017 • edited by ghost Loading

alastairs commented Jul 26, 2017

kylos101 commented Nov 26, 2017

kylos101 commented Nov 26, 2017

fejta-bot commented Feb 26, 2018

rmorrise commented Mar 28, 2018

rmorrise commented Mar 28, 2018

pxlphile commented May 15, 2018

fejta-bot commented Aug 13, 2018

rmorrise commented Aug 13, 2018

fejta-bot commented Dec 18, 2018

fejta-bot commented Jan 17, 2019

douglaswth commented Jul 23, 2019

tstromberg commented Aug 27, 2019

douglaswth commented Oct 21, 2019

tstromberg commented Oct 22, 2019 • edited Loading

tstromberg commented Oct 22, 2019

douglaswth commented Oct 22, 2019

tstromberg commented Dec 16, 2019

spdfnet commented Dec 16, 2019

douglaswth commented Dec 16, 2019

fejta-bot commented Mar 15, 2020

fejta-bot commented Apr 15, 2020

mevam commented Jun 11, 2017 •

edited

Loading

Retrying.
E0611 12:27:47.608522 8356 start.go:133] Error starting host: Error creating host: Error creating machine: Error in driver during machine creation: open /Users/navy/.minikube/cache/iso/minikube-v0.18.0.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

mevam commented Jun 11, 2017 •

edited

Loading

Retrying.
E0611 12:40:23.765630 4284 start.go:133] Error starting host: Error getting state for host: machine does not exist

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

Retrying.
E0611 12:40:36.428003 9060 start.go:133] Error starting host: Error getting state for host: machine does not exist

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

ghost commented Jun 16, 2017 •

edited by ghost

Loading

tstromberg commented Oct 22, 2019 •

edited

Loading