Solving the mystery of CAP_PERFMON and its significance

DevOps Kubernetes
#1

Anyone have an idea how to solve that? What is even CAP_PERFMON ?

#2

it’s a kernel capability, I don’t know whey it is “unknown” in your kernel. OS?

#3

debian 10 running on arm64 (raspberrypi)

#4 
NAME     STATUS   ROLES           AGE     VERSION    INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION            CONTAINER-RUNTIME
honda    Ready    control-plane   2y15d   v1.24.17   172.23.1.201   <none>        Debian GNU/Linux 10 (buster)   5.10.0-0.deb10.16-arm64   <containerd://1.7.11>
suzuki   Ready    <none>          2y15d   v1.24.17   172.23.1.202   <none>        Debian GNU/Linux 10 (buster)   5.9.0-0.bpo.5-arm64       <containerd://1.7.11>
yamaha   Ready    <none>          2y15d   v1.24.17   172.23.1.203   <none>        Debian GNU/Linux 10 (buster)   5.9.0-0.bpo.5-arm64       <containerd://1.7.11>
root@honda:~# uname -a
Linux honda 5.10.0-0.deb10.16-arm64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) aarch64 GNU/Linux```
#5

very specific…
try to read here:
https://github.com/cri-o/cri-o/issues/4658
it seems a bug with CRI-O/runc

#6

that issue seems to be related to cri-o ? I’m running containerd…

#7

root@honda:~# apt install runc
Reading package lists… Done
Building dependency tree
Reading state information… Done
runc is already the newest version (1.0.0~rc6+dfsg1-3+deb10u2).

“Upgrading runc to runc-1.0.2-1 solves the issue for me as well”

Will try get later version of runc installed