search

containerd / containerd

An open and reliable container runtime
https://containerd.io
Apache License 2.0
17.22k stars 3.41k forks source link

containerd-stress - is the binary messed up? #10501

Open manchuwook opened 2 months ago

manchuwook commented 2 months ago

Description

When running charmed-kubernetes, I get the error containerd resource binary containerd-stress failed a version check which gives an exit error '2' when trying to run.

I dunno if this is a problem with juju or containerd, but I'll post on both forums.

Steps to reproduce the issue

  1. $juju deploy charmed-kubernetes --overlay canal-overlay.yaml --channel latest/stable ignore-loose-rpf
  2. juju status
  3. error shows up

Describe the results you received and expected

Charmed kubernetes properly creating the worker and controller

What version of containerd are you using?

containerd containerd.io 1.7.19 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41

Any other relevant information

$ containerd --version
containerd containerd.io 1.7.19 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
$ runc --version
runc version 1.7.19
commit: v1.1.13-0-g58aa920
spec: 1.0.2-dev
go: go1.21.12
libseccomp: 2.5.5
$ crictl info
WARN[0000] runtime connect using default endpoints: [unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
ERRO[0000] validate service connection: validate CRI v1 runtime API for endpoint "unix:///run/containerd/containerd.sock": rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /run/containerd/containerd.sock: connect: permission denied"
ERRO[0000] validate service connection: validate CRI v1 runtime API for endpoint "unix:///run/crio/crio.sock": rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /run/crio/crio.sock: connect: no such file or directory"
ERRO[0000] validate service connection: validate CRI v1 runtime API for endpoint "unix:///var/run/cri-dockerd.sock": rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /var/run/cri-dockerd.sock: connect: no such file or directory"
FATA[0000] validate service connection: validate CRI v1 runtime API for endpoint "unix:///var/run/cri-dockerd.sock": rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /var/run/cri-dockerd.sock: connect: no such file or directory"
$ uname -a
Linux area51 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun  7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Show configuration if it is related to CRI plugin.

No response

samuelkarp commented 2 months ago

containerd-stress is not a required part of containerd; it's a development program for stress-testing.

The containerd project doesn't directly package containerd for juju or charmed-kubernetes. Since the error shows up in juju status, have you rather than containerd have you reached out to the juju or charmed-kubernetes projects?

You can also look at the containerd log (journalctl -u containerd.service if you're using systemd, for example) to see if there are errors there.