# Kubeadm init errors

**URL:** <https://discuss.kubernetes.io/t/kubeadm-init-errors/16960>\
**Category:** General Discussions\
**Created:** [August 4, 2021, 12:13pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960 "2021-08-04T12:13:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dsilwon](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/dsilwon/32/8299_2.png) [@dsilwon](https://discuss.kubernetes.io/u/dsilwon)\
**Post date:** [August 4, 2021, 12:13pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960/1 "2021-08-04T12:13:53Z")

</div>

Dears,

I’ve some problems with cluster initialization on vm’s. I’ve got such errors:

```auto
Aug 4 13:43:05 k8smaster dockerd: time="2021-08-04T13:43:05.717395707+02:00" level=warning msg="Error getting v2 registry: Get \"https://k8s.gcr.io/v2/\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 4 13:43:05 k8smaster dockerd: time="2021-08-04T13:43:05.717447179+02:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://k8s.gcr.io/v2/\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 4 13:43:05 k8smaster dockerd: time="2021-08-04T13:43:05.719617335+02:00" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://k8s.gcr.io/v2/\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 4 13:44:25 k8smaster dockerd: time="2021-08-04T13:44:25.622479123+02:00" level=warning msg="Error getting v2 registry: Get \"https://k8s.gcr.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 4 13:44:25 k8smaster dockerd: time="2021-08-04T13:44:25.622573678+02:00" level=info msg="Attempting next endpoint for pull after error: Get \"https://k8s.gcr.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
Aug 4 13:44:25 k8smaster dockerd: time="2021-08-04T13:44:25.624445759+02:00" level=error msg="Handler for POST /v1.41/images/create returned error: Get \"https://k8s.gcr.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

```

### Cluster information:

[root@k8smaster log]# cat /etc/redhat-release  
Red Hat Enterprise Linux Server release 7.9 (Maipo)  
[root@k8smaster log]# rpm -qa |grep -e kube -e docker  
docker-ce-20.10.8-3.el7.x86\_64  
kubeadm-1.21.3-0.x86\_64  
kubernetes-cni-0.8.7-0.x86\_64  
docker-ce-cli-20.10.8-3.el7.x86\_64  
kubelet-1.21.3-0.x86\_64  
docker-scan-plugin-0.8.0-3.el7.x86\_64  
docker-ce-rootless-extras-20.10.8-3.el7.x86\_64  
kubectl-1.21.3-0.x86\_64  
[root@k8smaster log]#

I suppose that I’ve some network errors. Am I right? or nor?  
Is there any way to run kubeadm init through proxy?

Best Regards,  
Dan

---

<div class="post-metadata">

**Author:** ![protosam](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/protosam/32/7732_2.png) [@protosam](https://discuss.kubernetes.io/u/protosam)\
**Post date:** [August 4, 2021, 2:11pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960/2 "2021-08-04T14:11:11Z")

</div>

```auto
Client.Timeout exceeded while awaiting headers

```

Whenever you see “timeout” just think “blocked”. Something is blocking this from working. Check firewall rules (firewallcmd & iptables in RHEL based distros) and any networking hardware’s firewall rules.

---

<div class="post-metadata">

**Author:** ![dsilwon](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/dsilwon/32/8299_2.png) [@dsilwon](https://discuss.kubernetes.io/u/dsilwon)\
**Post date:** [August 4, 2021, 3:07pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960/3 "2021-08-04T15:07:26Z")

</div>

Is there any way to run ‘kubeadm init’ command through proxy?

---

<div class="post-metadata">

**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\
**Post date:** [August 4, 2021, 5:25pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960/4 "2021-08-04T17:25:33Z")

</div>

Image pulls are handled by whatever container runtime you use (looks like docker). Have you configured docker with the proxy config?

---

<div class="post-metadata">

**Author:** ![dsilwon](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/dsilwon/32/8299_2.png) [@dsilwon](https://discuss.kubernetes.io/u/dsilwon)\
**Post date:** [August 4, 2021, 5:37pm UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960/5 "2021-08-04T17:37:14Z")

</div>

@mrbobbytables

Probably no. It was standard installation in this way:

```auto
sudo yum-config-manager \
    --add-repo \
    https://download.docker.com/linux/centos/docker-ce.repo

sudo yum install -y docker-ce docker-ce-cli containerd.io

```

and docker.service is without proxy settings.

I was abble to add docker repo and install all needed packages.

What do you suggest?

---

<div class="post-metadata">

**Author:** ![dsilwon](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/dsilwon/32/8299_2.png) [@dsilwon](https://discuss.kubernetes.io/u/dsilwon)\
**Post date:** [August 5, 2021, 11:02am UTC](https://discuss.kubernetes.io/t/kubeadm-init-errors/16960/6 "2021-08-05T11:02:02Z")

</div>

Finally our Network Team opened me “the door” to out side and cluster initialization went without problem. Thanks for all suggestions.