fail to start cri-docker

[JiinJie]

I configed the cri-docker ,and it shows failed to start. I search the config file from the internet.
maybe it has some problems,

here are the environment:
environment: ubuntu22.04 server
cri-dockerd package: cri-dockerd-0.3.0.amd64.tgz
kubernetes version: 1.26
docker version : 20.10.22, build 3a2c30b

here are the configs:

cat <<"EOF" > /usr/lib/systemd/system/cri-docker.service
[Unit]
Description=CRI Interface for Docker Application Container Engine
Documentation=https://docs.mirantis.com
After=network-online.target firewalld.service docker.service
Wants=network-online.target
Requires=cri-docker.socket
[Service]
Type=notify
ExecStart=/usr/bin/cri-dockerd --network-plugin=cni --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.7
ExecReload=/bin/kill -s HUP $MAINPID
TimeoutSec=0
RestartSec=2
Restart=always
StartLimitBurst=3
StartLimitInterval=60s
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
Delegate=yes
KillMode=process
[Install]
WantedBy=multi-user.target
EOF

cat <<"EOF" > /usr/lib/systemd/system/cri-docker.socket
[Unit]
Description=CRI Docker Socket for the API
PartOf=cri-docker.service
[Socket]
ListenStream=%t/cri-dockerd.sock
SocketMode=0660
SocketUser=root
SocketGroup=docker
[Install]
WantedBy=sockets.target
EOF

[afbjorklund]

If you install units in a local /etc/systemd, they will override the packaged defaults in /usr/lib/systemd...

You can use systemctl cat, to see the combined result (just remove /etc/systemd/system/cri-docker.service)

The recommendation is to only use an override, and leave the original files from the package.

https://www.freedesktop.org/software/systemd/man/systemd.unit.html

---

dpkg -i cri-dockerd_0.3.0.3-0.ubuntu-jammy_amd64.deb

/etc/systemd/system/cri-docker.service.d/override.conf

[Service]
ExecStart=
ExecStart=/usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.7

This situation will improve, once there is a config file (#102)

[evol262]

@JiinJie is there a reason you aren't using the packaged deb?

[JiinJie]

If you install units in a local /etc/systemd, they will override the packaged defaults in /usr/lib/systemd...

You can use systemctl cat, to see the combined result (just remove /etc/systemd/system/cri-docker.service)

The recommendation is to only use an override, and leave the original files from the package.

https://www.freedesktop.org/software/systemd/man/systemd.unit.html

dpkg -i cri-dockerd_0.3.0.3-0.ubuntu-jammy_amd64.deb

/etc/systemd/system/cri-docker.service.d/override.conf

[Service]
ExecStart=
ExecStart=/usr/bin/cri-dockerd --container-runtime-endpoint fd:// --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.7

This situation will improve, once there is a config file (#102)

yeah,it works.thanks a lot

[JiinJie]

@evol262 ha-ha, The answer was right in front of me

[afbjorklund]

The answer was right in front of me

Not sure about that, the upstream documentation seems to only give half of the real answer ?

Docker Engine
On each of your nodes, install Docker for your Linux distribution as per Install Docker Engine.
Install cri-dockerd, following the instructions in that source code repository.

Overriding the sandbox (pause) image
The cri-dockerd adapter accepts a command line argument for specifying which container image to use as the Pod infrastructure container (“pause image”). The command line argument to use is --pod-infra-container-image.

Specifically, it doesn't mention anything about packages or systemd - or broken socket detection.

Found multiple CRI endpoints on the host. Please define which one do you wish
to use by setting the 'criSocket' field in the kubeadm configuration file:
unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock