Minikube: (China) Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) ,

[cherish3620]

重现问题所需的命令：

失败的命令的完整输出：

minikube logs命令的输出：

minikube start
😄 minikube v1.3.1 on Darwin 10.13.4
🔥 Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
🐳 Preparing Kubernetes v1.15.2 on Docker 18.09.8 ...
E0905 20:42:26.337080 28857 start.go:558] Error caching images: Caching images for kubeadm: caching images: caching image /Users/jianjian5/.minikube/cache/images/k8s.gcr.io/pause_3.1: fetching remote image: Get https://k8s.gcr.io/v2/: dial tcp 64.233.189.82:443: i/o timeout
❌ Unable to load cached images: loading cached images: loading image /Users/jianjian5/.minikube/cache/images/k8s.gcr.io/coredns_1.3.1: stat /Users/jianjian5/.minikube/cache/images/k8s.gcr.io/coredns_1.3.1: no such file or directory
💾 Downloading kubelet v1.15.2
💾 Downloading kubeadm v1.15.2
🚜 拉取镜像 ...
🚀 正在启动 Kubernetes ...

💣 Error starting cluster: cmd failed: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--data-minikube,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap
[init] Using Kubernetes version: v1.15.2
[preflight] Running pre-flight checks
[WARNING Service-Docker]: docker service is not enabled, please run 'systemctl enable docker.service'
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.15.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.15.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.15.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.15.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.1: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.3.10: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.3.1: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...

: Process exited with status 1

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose

使用的操作系统版本：
mac os

[tstromberg]

我相信中国的伟大防火墙可能会干扰您访问Kubernetes图像。

您可以使用以下命令配置代理：https://minikube.sigs.k8s.io/docs/reference/networking/proxy/

要测试代理是否有效，您可以尝试：

env http_proxy=<address> https_proxy=<address> curl https://k8s.gcr.io/robots.txt

请让我知道这可不可以帮你。

[cherish3620]

Appreciate!
Thanks

在 2019年9月6日，上午1:02，Thomas Strömberg [e-mail] 写道：

我相信中国的伟大防火墙可能会干扰您访问Kubernetes图像。

您可以使用以下命令配置代理：https://minikube.sigs.k8s.io/docs/reference/networking/proxy/ https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
要测试代理是否有效，您可以尝试：

env http_proxy =

https_proxy =

curl https：// k8s.gcr.io / robots.txt

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/5269?email_source=notifications&email_token=AB7RGJKVHAV5PHCTNF2FNGTQIE3SZA5CNFSM4IT5NIH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD57354A#issuecomment-528465648, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7RGJPAD2U3MGIR2BYOE6LQIE3SZANCNFSM4IT5NIHQ.

[sharifelgamal]

Workaround found, closing this.