Today, when I added a new Kubernetes (v1.30.0) node into the cluster, the new node showed the following error:
invalid capacity 0 on image filesystem
On the new node, I am using containerd. It seems it could not detect the image filesystem size. Here is the output of the lsblk command:
root@iZhp33cq6mvrjo8mzatgrmZ:/etc/containerd# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
vda 254:0 0 40G 0 disk
├─vda1 254:1 0 1M 0 part
├─vda2 254:2 0 191M 0 part /boot/efi
└─vda3 254:3 0 39.8G 0 part /
This is the containerd version info:
root@iZhp33cq6mvrjo8mzatgrmZ:/etc/containerd# containerd --version
containerd github.com/containerd/containerd 1.6.20~ds1 1.6.20~ds1-1+b1
Am I missing some configuration on the new nodes? The new node's pods are always in the Waiting state.
What should I do to fix this issue??
Asked by Dolphin
(791 rep)
Nov 24, 2024, 11:09 AM
Last activity: Jun 9, 2025, 01:06 PM
Last activity: Jun 9, 2025, 01:06 PM