Kubernetes version: 1.26.3
Cloud being used: GCP and AWS
Installation method: Official Docker & K8s, with cri-docker
Host OS: Ubuntu 22.04 (Jammy)
CNI and version: latest version
CRI and version: latest version
hello, i’ve same problem

i’m using ubuntu, and cri dockerd, also using latest version kubernetes

i’ve been try to:
allow all ports
deactivate ufw
kubeadm reset --cri-socket unix:///var/run/cri-dockerd.sock
kubeadm init --cri-socket unix:///var/run/cri-dockerd.sock
try to rebuild vm
try on gcp also aws
checked forum and try many same advice

but still having problem

and this is my output container logs

image1739×242 12.2 KB
please help me

thank you very much!
              
when i checked it’s not showing v2 anymore,

is that mean i used v1 for default cgroups?
root@master:~# sudo cat /sys/fs/cgroup/cgroup.controllers
cpuset cpu io memory hugetlb pids rdma misc
i decide create from scratch again on my AWS but still same error, here’s my output if i ran that command:
ubuntu@ip-172-31-25-66:~$  stat -fc %T /sys/fs/cgroup/
cgroup2fs
and here’s my kubelet services status
ubuntu@ip-172-31-25-66:~$ sudo service kubelet status
● kubelet.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/kubelet.service.d
             └─10-kubeadm.conf
     Active: activating (auto-restart) (Result: exit-code) since Mon 2023-04-03 21:21:27 UTC; 8s ago
       Docs: https://kubernetes.io/docs/home/
    Process: 11309 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=1/FAILURE)
   Main PID: 11309 (code=exited, status=1/FAILURE)
        CPU: 79ms
              
You’ll need to make sure both Kubernetes and your container runtime are set to use systemd as the cgroup driver.
I’m not sure about instructions with docker, but for containerd you need to use 1.4+ and set the option in the config