-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Closed
Labels
Description
Description
I have installed containerd on NixOS on a raspberry pi, and it raises errors constantly with the following messages
Jul 22 09:27:03 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:03.545909051Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:03 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:03.657185766Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:03 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:03.768858588Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:03 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:03.880564225Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:04 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:04.004382141Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:04 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:04.115368876Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:04 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:04.229788479Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:04 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:04.340334811Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:04 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:04.450108801Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
Jul 22 09:27:04 cluster-master-1 containerd[1026]: time="2024-07-22T09:27:04.561611845Z" level=error msg="Status failed" error="invalid UUID length: 0: unknown"
My containerd instance is configured for k8s.
Steps to reproduce the issue
- Install NixOS on arm64
- Add the following config
virtualisation.containerd = {
enable = true;
settings.plugins = {
"io.containerd.internal.v1.opt".path = "/var/lib/containerd/opt";
"io.containerd.grpc.v1.cri" = {
sandbox_image = "registry.k8s.io/pause:3.9";
containerd = {
snapshotter = "overlayfs";
runtimes.runc.options.SystemdCgroup = true;
};
};
};
};
Although my issue arises on NixOS, I have no idea whether it is linked to nixos or not
Describe the results you received and expected
Containerd was expected to work properly, and ctr can pull images and run containers, however, the kubelet fails with sanity check errors.
What version of containerd are you using?
containerd github.com/containerd/containerd v1.7.16 v1.7.16
Any other relevant information
$ runc --version
runc version 1.1.12
spec: 1.0.2-dev
go: go1.22.4
libseccomp: 2.5.5
$ crictl info
E0722 09:31:32.586917 1731 remote_runtime.go:633] "Status from runtime service failed" err="rpc error: code = Unknown desc = invalid UUID length: 0: unknown"
FATA[0000] getting status of runtime: rpc error: code = Unknown desc = invalid UUID length: 0: unknown
$ uname -a
Linux cluster-master-1 6.1.63 #1-NixOS SMP Tue Jan 1 00:00:00 UTC 1980 aarch64 GNU/Linux
Show configuration if it is related to CRI plugin.
oom_score = 0
root = "/var/lib/containerd"
state = "/run/containerd"
version = 2
[grpc]
address = "/run/containerd/containerd.sock"
[plugins]
[plugins."io.containerd.grpc.v1.cri"]
sandbox_image = "registry.k8s.io/pause:3.9"
[plugins."io.containerd.grpc.v1.cri".cni]
bin_dir = "/opt/cni/bin"
max_conf_num = 0
[plugins."io.containerd.grpc.v1.cri".containerd]
snapshotter = "overlayfs"
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
runtime_type = "io.containerd.runc.v2"
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
SystemdCgroup = true
[plugins."io.containerd.internal.v1.opt"]
path = "/var/lib/containerd/opt"
Reactions are currently unavailable