You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that running kubelet with runc makes it impossible to access container stats.
May 31 07:24:05 atomictest-4 runc[3945]: E0531 07:24:05.036706 3953 summary.go:92] Failed to get system container stats for"/system.slice": failed to get cgroup stats for"/system.slice": failed to get container info for"/system.slice": unknown container "/system.slice"
I tried to run kubelet directly (not via runc) /var/lib/containers/atomic/kubelet.0/rootfs/usr/bin/kubelet with the same command line argument and then it can access container stats.
It seems to me that when running with runc it cannot access host system /sys/fs/cgroup/systemd/system.slice which is necessary to collect container stats.
The text was updated successfully, but these errors were encountered:
It seems that running kubelet with runc makes it impossible to access container stats.
I tried to run kubelet directly (not via
runc
)/var/lib/containers/atomic/kubelet.0/rootfs/usr/bin/kubelet
with the same command line argument and then it can access container stats.It seems to me that when running with
runc
it cannot access host system/sys/fs/cgroup/systemd/system.slice
which is necessary to collect container stats.The text was updated successfully, but these errors were encountered: