when the CRI runtime is containerd, How to quickly troubleshoot which container on a node is using a lot of rootfs

Asked Aug 04 '23 at 11:15

Active Aug 04 '23 at 11:15

Viewed 21 times

-1

when the CRI runtime is docker, I can use command "docker system df -v" to see docker disk usage and find which container is writing data to rootfs After k8s 1.24, the common cri runtime becomes containerd, how to find it quickly?

Is there a more command or convenient tool?

asked Aug 04 '23 at 11:15

Gale

How is this question related to programming? – Turing85 Aug 04 '23 at 11:18
Please write your question which shows your effort and still not being able to find the answer. This information you can find on google easily. – tauqeerahmad24 Aug 08 '23 at 07:54

when the CRI runtime is containerd, How to quickly troubleshoot which container on a node is using a lot of rootfs

0 Answers0