Welcome to the Linux Foundation Forum!

Lab 1c - unknown service runtime.v1alpha2.RuntimeService

I've encountered this error when executing this: sudo kubeadm init
But i found a solution with the below. Will this cause any issues?

~/labsys$ sudo kubeadm init
[init] Using Kubernetes version: v1.24.0
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR CRI]: container runtime is not running: output: time="2022-05-10T20:46:49Z" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher
~/labsys$ sudo rm /etc/containerd/config.toml
~/labsys$ sudo systemctl restart containerd
~/labsys$ sudo kubeadm init

Comments

  • In this case you're initializing Kubernetes using containerd rather than Docker as the underlying container runtime.

    The only effect this will have is that you will not be able to see the Kubernetes containers using sudo docker container ls. Otherwise, Kubernetes will still run the containers and you should be able to proceed with the lab.

    To view the containers you can use sudo crictl ps instead (it will generate warnings as it tries to look up containers using other potential runtimes)

  • joshl
    joshl Posts: 37
    edited May 10

    thanks Christian.
    What would be the correct alternative solution to keep using /etc/containerd/config.toml?

Categories

Upcoming Training