Minikube: Temporary download error: Get minikube-v0.34.0.iso: net/http: TLS handshake timeout

Created on 27 Feb 2019  路  4Comments  路  Source: kubernetes/minikube

Mac OS: 10.14.3

  • install kubectl (vers. 1.13.3)
  • install VirtualBox (vers. 6.0.4)
  • install minikube (vers. 0.34.1)
  • run minikube start

Out:

minikube v0.34.1 on darwin (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.34.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.34.0.iso: net/http: TLS handshake timeout
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.34.0.iso: net/http: TLS handshake timeout
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.34.0.iso: net/http: TLS handshake timeout
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.34.0.iso: net/http: TLS handshake timeout
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v0.34.0.iso: net/http: TLS handshake timeout

馃樋  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
馃憠  https://github.com/kubernetes/minikube/issues/new
arenetworking causfirewall-or-proxy prioritawaiting-more-evidence triagneeds-information

Most helpful comment

solution found: use

sudo minikube start

All 4 comments

solution found: use

sudo minikube start

This sounds like a some sort of proxy configuration may be necessary to access storage.googleapis.com - please see https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md

I'm closing this issue as it hasn't seen activity in awhile, and it's unclear if this issue still exists. If this issue does continue to exist in the most recent release of minikube, please feel free to re-open it.

Thank you for opening the issue!

I have reproduced this problem, it may be a network cause. Sometimes it works, sometimes not.

Was this page helpful?
0 / 5 - 0 ratings