cri-o 1.20.1 fails to run privileged pods: unknown capability "CAP_PERFMON" #4658
Description
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 15s default-scheduler Successfully assigned kube-system/kube-proxy-7j8zj to nas
Warning Failed 14s (x2 over 14s) kubelet Error: container create failed: time="2021-03-15T07:39:31+01:00" level=error msg="container_linux.go:370: starting container process caused: unknown capability \"CAP_PERFMON\""
Normal Pulled 1s (x3 over 14s) kubelet Container image "k8s.gcr.io/kube-proxy:v1.20.4" already present on machine
Warning Failed 1s kubelet Error: container create failed: time="2021-03-15T07:39:44+01:00" level=error msg="container_linux.go:370: starting container process caused: unknown capability \"CAP_PERFMON\""
crio --version
INFO[0000] Starting CRI-O, version: 1.20.1, git: 0e6266bc8b26e7f8c1b85df3af7af1dcb50ce813(clean)
crio version 1.20.1
Version: 1.20.1
GitCommit: 0e6266bc8b26e7f8c1b85df3af7af1dcb50ce813
GitTreeState: clean
BuildDate: 2021-03-12T02:24:13Z
GoVersion: go1.15.2
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
And 1.20.0 release can't be installed anymore because it was removed from repository: #4657
Problem seems to be related to #4466
1.20.1 release has different gocapability than 1.20.0: https://github.com/cri-o/cri-o/blob/v1.20.1/go.mod#L54
But cri-o-runc package wasn't updated in the repos, still 1.0.0~rc92.3: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04/amd64/