解决minukube启动时因为未设代理导致的启动失败错误
我用的windows平臺下的minikube是從下面這個鏈接下載的:
https://storage.googleapis.com/minikube/releases/v0.25.2/minikube-windows-amd64.exe
啟動時,遇到如下錯誤消息:
Temporary download error: Get https://storage. googleapis. com/minikube/iso/minikube-vo.25.1.iso: dial tcp 1727.160.80:443: connectex: A connection attempt failed because the connected party did not properly respond aftoa period of time, or established connection failed because connected host has failed to respond…
Retrying
0516 17:21:37.398760 23232 start. go:165] Error starting host: Error attempting to cache minikube ISO from: Error downloading Minikube ISO: failed to download: failed to download to temp file: download failed: 5 ero(s) occurred:
Temporary download error: Get https://storage. googleapis. com/minikube/iso/minikube-vo.25.1.iso: read tcp 10…197.181:59356->172.217. 160.80:443: wsarecv: A connection attempt failed because the connected party did notperly respond after a period of time, or established connection failed because connected host has failed to reond.
Temporary download error: Get https://storage .googleapis. com/minikube/iso/minikube-vo.25.1.iso: dial tcp 1727.160.80:443: connectex: A connection attempt failed because the connected party did not properly respond aftoa 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-vo.25.1.iso: dial tcp 1727.160.80:443: connectex: A connection attempt failed because the connected party did not properly respond aftoa 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-vo.25.1.iso: dial tcp 17217.160.80:443: connectex: A connection attempt failed because the connected party did not properly respond aftoa 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-vo. 25.1. iso: dial tcp 172
解決方案:
minikube start
–docker-env HTTP_PROXY=http://proxy.sha.sap.corp:8080/
–docker-env HTTPS_PROXY=http://proxy.sha.sap.corp:8080/
–docker-env NO_PROXY=index.docker.io,
registry.hub.docker.com,
registry-1.docker.io,
registry.docker-cn.com,
registry-mirror-cache-cn.oss-cn-shanghai.aliyuncs.com,
192.168.99.100
–registry-mirror https://registry.docker-cn.com
Make sure VirtualBox is installed and VBoxManage is in the path
要獲取更多Jerry的原創(chuàng)文章,請關(guān)注公眾號"汪子熙":
總結(jié)
以上是生活随笔為你收集整理的解决minukube启动时因为未设代理导致的启动失败错误的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: Intel CEO基辛格第一次以新身份访
- 下一篇: 20万元买特斯拉?陶琳甩出5张图:中国价