Minikube: unable to cache ISO: connection failed because connected host has failed to respond.

Created on 21 Mar 2019  路  4Comments  路  Source: kubernetes/minikube





C:\Users\saravanaprasath_s>minikube start
o   minikube v0.35.0 on windows (amd64)
>   Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
@   Downloading Minikube ISO ...
!   Unable to start VM: unable to cache ISO: https://storage.googleapis.com/minikube/iso/minikube-v0.35.0.iso: failed to download: failed to download to temp file: download failed: 5 error(s) occurred
:

* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.35.0.iso: dial tcp 216.58.207.144:443: connectex: A connection attempt failed because the connected party did no
t properly respond after a period of time, or established connection failed because connected host has failed to respond.
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.35.0.iso: dial tcp 216.58.207.144:443: connectex: A connection attempt failed because the connected party did no
t properly respond after a period of time, or established connection failed because connected host has failed to respond.
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.35.0.iso: dial tcp 216.58.207.144:443: connectex: A connection attempt failed because the connected party did no
t properly respond after a period of time, or established connection failed because connected host has failed to respond.
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.35.0.iso: dial tcp 216.58.207.144:443: connectex: A connection attempt failed because the connected party did no
t properly respond after a period of time, or established connection failed because connected host has failed to respond.
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.35.0.iso: dial tcp 216.58.207.144:443: connectex: A connection attempt failed because the connected party did no
t properly respond after a period of time, or established connection failed because connected host has failed to respond.
causfirewall-or-proxy prioritawaiting-more-evidence triagneeds-information

Most helpful comment

Had this issue too due to crappy connectivity in China.

It would be best if it can auto-resume a failed download. Currently it starts from scratch.

Also, if you want to download manually (always a good option) and then provide the ISO it's unclear where to place it. To save anyone else doing this time, please be aware you have to place it in ~/.minikube/cache/iso/.

However, it will want to download a bunch more files so basically you are stuck with supplying a proxy or having patience for its brittle download implementation. Sigh.

All 4 comments

A firewall is likely blocking minikube from reaching the internet. You may need to configure minikube to use a proxy.

Please see: https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md

friendly ping @saravanaprasaths - did the proxy help with your issue?

friendly ping @saravanaprasaths - did the proxy help with your issue?

Yup, it was a firewall. in open network I was able to download.

Had this issue too due to crappy connectivity in China.

It would be best if it can auto-resume a failed download. Currently it starts from scratch.

Also, if you want to download manually (always a good option) and then provide the ISO it's unclear where to place it. To save anyone else doing this time, please be aware you have to place it in ~/.minikube/cache/iso/.

However, it will want to download a bunch more files so basically you are stuck with supplying a proxy or having patience for its brittle download implementation. Sigh.

Was this page helpful?
0 / 5 - 0 ratings