You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the error/improvement to an existing document or image
In the manual installation section of kubernetes tutorial documentation the user have to choose one of the runtime engines.
The instruction for CRI-O is incomplete and lacks the section describing how to configure kubelet to use systemd as the cgroup driver, which is also necessary for cri-o. Without it, kubelet is not able to spawn any container.
The configuration is exactly the same as for containerd runtime, and should be done BEFORE enabling kubelet and crio service:
# configure kubelet to use systemd as a cgroup driver
sudo mkdir -p /etc/systemd/system/kubelet.service.d/
cat << EOF | sudo tee /etc/systemd/system/kubelet.service.d/10-cgroup-driver.conf
[Service]
Environment="KUBELET_EXTRA_ARGS=--cgroup-driver=systemd"
EOF
# enable kubelet
sudo systemctl enable kubelet.service
# enable and start cri-o
sudo systemctl enable --now crio.service
Screenshots
Environment (please complete the following):
Clear Linux OS version: 3372
Additional context
The text was updated successfully, but these errors were encountered:
Describe the error/improvement to an existing document or image
In the manual installation section of kubernetes tutorial documentation the user have to choose one of the runtime engines.
The instruction for CRI-O is incomplete and lacks the section describing how to configure kubelet to use systemd as the cgroup driver, which is also necessary for cri-o. Without it, kubelet is not able to spawn any container.
The configuration is exactly the same as for containerd runtime, and should be done BEFORE enabling kubelet and crio service:
Screenshots
Environment (please complete the following):
Additional context
The text was updated successfully, but these errors were encountered: