Kubeadm init failing due to 'kubeadm config images pull" failure

General Discussions
1

Hi All,
I am trying to setup kubernetes cluster with kubeadm, kubernetes. I am using version 1.30.3 kubernetes. When I am executing the command in dry mode, setup is showing successful .
kubeadm init --config cluster_config.yaml --ignore-preflight-errors=NumCPU --dry-run
However, when running kubeadm init without dry-run , when it goes for pulling image using “kubeadm config images pull” it showing Client.Timeout exceeded while awaiting headers
I am trying to setup on debian 12 virtual machine with cri-dockerd verison =0.3.15.3-0

Cluster information:

Trying to setup single node k8s cluster.
Kubernetes version: 1.30.3
Docker version : 27.1.1

Cloud being used: Machine is running in vCenter (vmware) host.
Installation method:
Host OS: Debian 12
CNI and version: NA
CRI and version: cri-dockerd with version 0.3.15.3-0

[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'
I0729 07:40:03.367227   17305 checks.go:830] using image pull policy: IfNotPresent
I0729 07:40:03.409156   17305 checks.go:870] pulling: registry.k8s.io/kube-apiserver:v1.30.3
I0729 07:41:49.127386   17305 checks.go:870] pulling: registry.k8s.io/kube-controller-manager:v1.30.3
I0729 07:43:04.336827   17305 checks.go:870] pulling: registry.k8s.io/kube-scheduler:v1.30.3
I0729 07:44:50.214758   17305 checks.go:870] pulling: registry.k8s.io/kube-proxy:v1.30.3
I0729 07:46:23.295864   17305 checks.go:870] pulling: registry.k8s.io/coredns/coredns:v1.11.1
I0729 07:47:53.608212   17305 checks.go:870] pulling: registry.k8s.io/pause:3.9
I0729 07:49:24.185039   17305 checks.go:870] pulling: registry.k8s.io/etcd:3.5.12-0
[preflight] Some fatal errors occurred:
        [ERROR ImagePull]: failed to pull image registry.k8s.io/kube-apiserver:v1.30.3: output: E0729 07:41:49.094359   17354 remote_image.go:180] "PullImage from image service failed" err="rpc error: code = Unknown desc = Error response from daemon: Get \"https://registry.k8s.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" image="registry.k8s.io/kube-apiserver:v1.30.3"
time="2024-07-29T07:41:49-04:00" level=fatal msg="pulling image: Error response from daemon: Get \"https://registry.k8s.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 registry.k8s.io/kube-controller-manager:v1.30.3: output: E0729 07:43:04.311234   17392 remote_image.go:180] "PullImage from image service failed" err="rpc error: code = Unknown desc = Error response from daemon: Get \"https://registry.k8s.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" image="registry.k8s.io/kube-controller-manager:v1.30.3"
time="2024-07-29T07:43:04-04:00" level=fatal msg="pulling image: Error response from daemon: Get \"https://registry.k8s.io/v2/\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)", error: exit status 1

Attaching screenshot of error observed after Timeout.

Screenshot (229)
Screenshot (229)1920×1080 303 KB

Please suggest some debugging to resolve the issue.
Thanks.