Counting cap_perform capability in capsh command output and getting 0

DevOps Kubernetes
1

root@honda:~# capsh --print | grep cap_perform | wc -l
0

2

You’ve got a typo in there, you want cap_perfmon

3 
0
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
root@honda:~# uname -r
5.10.0-0.deb10.16-arm64
root@honda:~# ```
4

5.10 kernel should support cap_perfmon from what I read, but this might not be true for arm64 ?
And if so, how can I make kube-proxy work without cap_perfmon? Does it really need it…?

5

I haven’t seen this, but https://github.com/containerd/containerd/issues/6009 sounds like it, and has a possible fix

6

No luck. I will try just upgrade cluster step by step to latest version.

7

But this one feels tricky… :disappointed: