minikube: none: VM is unable to access k8s.gcr.io -> exceeded while awaiting headers
[root@laptop ~]# minikube start --vm-driver=none đ minikube v1.6.1 on Fedora 29 ⨠Selecting ânoneâ driver from user configuration (alternates: []) 𤚠Running on localhost (CPUs=8, Memory=7735MB, Disk=15054MB) ⌠âšď¸ OS release is Fedora 29 (Workstation Edition) â ď¸ VM is unable to access k8s.gcr.io, you may need to configure a proxy or set --image-repository đł Preparing Kubernetes v1.17.0 on Docker â19.03.4â ⌠đž Downloading kubelet v1.17.0 đž Downloading kubeadm v1.17.0 đ Pulling images ⌠â Unable to pull images, which may be OK: running cmd: â/bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml"â: /bin/bash -c âsudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yamlâ: exit status 1 stdout:
stderr: W1212 11:02:01.365969 19837 common.go:77] your configuration file uses a deprecated API spec: âkubeadm.k8s.io/v1beta1â. Please use âkubeadm config migrate --old-config old.yaml --new-config new.yamlâ, which will write the new, similar spec using a newer API version. W1212 11:02:01.366538 19837 common.go:77] your configuration file uses a deprecated API spec: âkubeadm.k8s.io/v1beta1â. Please use âkubeadm config migrate --old-config old.yaml --new-config new.yamlâ, which will write the new, similar spec using a newer API version. W1212 11:02:01.368659 19837 validation.go:28] Cannot validate kubelet config - no validator is available W1212 11:02:01.368670 19837 validation.go:28] Cannot validate kube-proxy config - no validator is available failed to pull image âk8s.gcr.io/kube-apiserver:v1.17.0â: 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 To see the stack trace of this error execute with --v=5 or higher
đ Launching Kubernetes âŚ
đŁ Error starting cluster: init failed. cmd: â/bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailableâetc-kubernetes-manifests,DirAvailableâvar-lib-minikube,DirAvailableâvar-lib-minikube-etcd,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"â: /bin/bash -c âsudo env PATH=/var/lib/minikube/binaries/v1.17.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailableâetc-kubernetes-manifests,DirAvailableâvar-lib-minikube,DirAvailableâvar-lib-minikube-etcd,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â: exit status 1 stdout: [init] Using Kubernetes version: v1.17.0 [preflight] Running pre-flight checks [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â
stderr:
W1212 11:02:16.549054 20140 common.go:77] your configuration file uses a deprecated API spec: âkubeadm.k8s.io/v1beta1â. Please use âkubeadm config migrate --old-config old.yaml --new-config new.yamlâ, which will write the new, similar spec using a newer API version.
W1212 11:02:16.549673 20140 common.go:77] your configuration file uses a deprecated API spec: âkubeadm.k8s.io/v1beta1â. Please use âkubeadm config migrate --old-config old.yaml --new-config new.yamlâ, which will write the new, similar spec using a newer API version.
W1212 11:02:16.551904 20140 validation.go:28] Cannot validate kube-proxy config - no validator is available
W1212 11:02:16.551914 20140 validation.go:28] Cannot validate kubelet config - no validator is available
[WARNING Firewalld]: firewalld is active, please ensure ports [8443 10250] are open or your cluster may not function correctly
[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 Swap]: running with swap on is not supported. Please disable swap
[WARNING FileExisting-socat]: socat not found in system path
[WARNING Hostname]: hostname âminikubeâ could not be reached
[WARNING Hostname]: hostname âminikubeâ: lookup minikube on 192.168.43.33:53: no such host
[WARNING Service-Kubelet]: kubelet service is not enabled, please run âsystemctl enable kubelet.serviceâ
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.17.0: 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.17.0: 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.17.0: 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.17.0: 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.4.3-0: 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.6.5: 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=...
To see the stack trace of this error execute with --v=5 or higher
đż Sorry that minikube crashed. If this was unexpected, we would love to hear from you: đ https://github.com/kubernetes/minikube/issues/new/choose
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (2 by maintainers)
Got a solution for this issue. For minikube to pull images it needs to have a public network connection which can be created by Virtual switch in HyperV.
Solves below issues while starting minikube: Ths issue - VM is unable to access k8s.gcr.io - Unable to pull images,
In the end for me it was dnsmasq messing with my connection. Turning it off solved the issue.
When I run
curl https://k8s.gcr.io/the output:
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8"> <TITLE>302 Moved</TITLE></HEAD><BODY>302 Moved
The document has moved here. </BODY></HTML>I met the same problem when using hyperkit as driver. Delete minikube and use another driver(e.g. virtualbox) is a quick solution.
PS C:\Windows\system32> minikube start --vm-driver=hyperv
stderr: W1224 06:49:16.080769 3673 common.go:77] your configuration file uses a deprecated API spec: âkubeadm.k8s.io/v1beta1â. Please use âkubeadm config migrate --old-config old.yaml --new-config new.yamlâ, which will write the new, similar spec using a newer API version. W1224 06:49:16.081889 3673 common.go:77] your configuration file uses a deprecated API spec: âkubeadm.k8s.io/v1beta1â. Please use âkubeadm config migrate --old-config old.yaml --new-config new.yamlâ, which will write the new, similar spec using a newer API version. W1224 06:49:16.084063 3673 validation.go:28] Cannot validate kube-proxy config - no validator is available W1224 06:49:16.084132 3673 validation.go:28] Cannot validate kubelet config - no validator is available failed to pull image âk8s.gcr.io/kube-apiserver:v1.17.0â: 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 To see the stack trace of this error execute with --v=5 or higher