cri-o: /var/run/crio/crio.sock doesn't exist

Description

After cri-o installment on Ubuntu, the /var/run/crio/crio.sock dose not exist. And kubelet will run into error like “failed to run Kubelet: failed to create kubelet: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: Error while dialing dial unix /var/run/crio/crio.sock: connect: no such file or directory””

Steps to reproduce the issue:

. /etc/os-release sudo sh -c “echo ‘deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/x${NAME}_${VERSION_ID}/ /’ > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list” wget -nv https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/x${NAME}_${VERSION_ID}/Release.key -O- | sudo apt-key add - sudo apt-get update sudo apt-get install cri-o-1.17

Output of crio --version:

crio -v
crio version 1.17.4
cat /proc/version
Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 15 (7 by maintainers)

Most upvoted comments

I got when I run sudo crictl version this is my /etc/crictl.yaml:

runtime-endpoint: "unix:///var/run/crio/crio.sock"
image-endpoint: "unix:///var/run/crio/crio.sock"
cgroup-manager: systemd

timeout: 10
debug: true
pull-image-on-create: false

this is the error:

$ sudo crictl version
FATA[0010] failed to connect: failed to connect, make sure you are running as root and the runtime has been started: context deadline exceeded

So I try to run $ sudo crio and I got the following error:

$ sudo crio
INFO[2021-04-26 14:03:55.963576795Z] Starting CRI-O, version: 1.21.0, git: bc1ef35a932acc2f6f3b6d3eb19a4f68aa9423f6(clean)
INFO[2021-04-26 14:03:55.963751537Z] Node configuration value for hugetlb cgroup is true
INFO[2021-04-26 14:03:55.963766932Z] Node configuration value for pid cgroup is true
ERRO[2021-04-26 14:03:55.963820380Z] Node configuration validation for memoryswap cgroup failed: node not configured with memory swap
INFO[2021-04-26 14:03:55.963831431Z] Node configuration value for memoryswap cgroup is false
INFO[2021-04-26 14:03:55.970342461Z] Node configuration value for systemd CollectMode is true
INFO[2021-04-26 14:03:55.973805833Z] Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL
INFO[2021-04-26 14:03:55.975206615Z] Using conmon executable: /usr/bin/conmon
INFO[2021-04-26 14:03:55.977227202Z] Conmon does support the --sync option
INFO[2021-04-26 14:03:55.977320147Z] No seccomp profile specified, using the internal default
INFO[2021-04-26 14:03:55.977349758Z] Installing default AppArmor profile: crio-default
INFO[2021-04-26 14:03:56.015806482Z] Found CNI network crio (type=bridge) at /etc/cni/net.d/11-crio-ipv4-bridge.conf
INFO[2021-04-26 14:03:56.015892818Z] Updated default CNI network name to crio
ERRO[2021-04-26 14:03:56.054267575Z] Remove /var/lib/crio/clean.shutdown: no such file or directory

Rizary on Apr 26, 2021