when i use

kubeadm init --config kubeadm.yaml

it throw out the following error:

ubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.

Unfortunately, an error has occurred:
        timed out waiting for the condition

This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
        - 'systemctl status kubelet'
        - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all running Kubernetes containers by using crictl:
        - 'crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock ps -a | grep kube | grep -v pause'
        Once you have found the failing container, you can inspect its logs with:
        - 'crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

while when check the kubelet status it show the following error:

root@k8s-master:/home/zl/k8s/kube-1.25.3# systemctl status kubelet > test.log
root@k8s-master:/home/zl/k8s/kube-1.25.3# cat test.log
● kubelet.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-05-15 13:43:13 CST; 18min ago
       Docs: https://kubernetes.io/docs/home/
   Main PID: 81690 (kubelet)
      Tasks: 14 (limit: 8069)
     Memory: 26.9M
        CPU: 25.930s
     CGroup: /system.slice/kubelet.service
             └─81690 /usr/bin/kubelet --container-runtime-endpoint=/var/run/cri-dockerd.sock

5月 15 14:01:13 k8s-master kubelet[81690]: E0515 14:01:13.972575   81690 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized"
5月 15 14:01:18 k8s-master kubelet[81690]: E0515 14:01:18.997357   81690 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized"
5月 15 14:01:24 k8s-master kubelet[81690]: E0515 14:01:24.023611   81690 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized"

any suggestion?

and my k8s version is 1.25.3

anyone come across the same issue?