Invalid capacity 0 on image filesystem

개요[ | ]

invalid capacity 0 on image filesystem
$ kubectl get events | grep node
24m         Normal    Starting                  node/ip-10-100-105-140             Starting kube-proxy.
24m         Normal    Starting                  node/ip-10-100-105-140             Starting kubelet.
24m         Warning   InvalidDiskCapacity       node/ip-10-100-105-140             invalid capacity 0 on image filesystem
24m         Normal    NodeHasSufficientMemory   node/ip-10-100-105-140             Node ip-10-100-105-140 status is now: NodeHasSufficientMemory
24m         Normal    NodeHasNoDiskPressure     node/ip-10-100-105-140             Node ip-10-100-105-140 status is now: NodeHasNoDiskPressure
24m         Normal    NodeHasSufficientPID      node/ip-10-100-105-140             Node ip-10-100-105-140 status is now: NodeHasSufficientPID
24m         Normal    NodeNotReady              node/ip-10-100-105-140             Node ip-10-100-105-140 status is now: NodeNotReady
24m         Normal    NodeAllocatableEnforced   node/ip-10-100-105-140             Updated Node Allocatable limit across pods
24m         Normal    NodeReady                 node/ip-10-100-105-140             Node ip-10-100-105-140 status is now: NodeReady
# journalctl -u kubelet | grep E03
Mar 23 12:54:52 kubeception-544bdb89f9-mxt9t kubelet[14951]: E0323 12:54:52.067742   14951 kubelet.go:1468] "Image garbage collection failed once. Stats initialization may not have completed yet" err="invalid capacity 0 on image filesystem"
Mar 23 12:54:52 kubeception-544bdb89f9-mxt9t kubelet[14951]: E0323 12:54:52.084980   14951 kubelet.go:2380] "Skipping pod synchronization" err="[container runtime status check may not have completed yet, PLEG is not healthy: pleg has yet to be successful]"
Mar 23 12:54:52 kubeception-544bdb89f9-mxt9t kubelet[14951]: E0323 12:54:52.185046   14951 kubelet.go:2380] "Skipping pod synchronization" err="container runtime status check may not have completed yet"
Mar 23 12:54:56 kubeception-544bdb89f9-mxt9t kubelet[14998]: E0323 12:54:56.123616   14998 run.go:74] "command failed" err="failed to run Kubelet: validate service connection: validate CRI v1 runtime API for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unavailable desc = server is not initialized yet: unavailable"
Mar 23 12:54:57 kubeception-544bdb89f9-mxt9t kubelet[15046]: E0323 12:54:57.318908   15046 kubelet_node_status.go:462] "Error getting the current node from lister" err="node \"kubeception-544bdb89f9-mxt9t\" not found"
Mar 23 12:54:57 kubeception-544bdb89f9-mxt9t kubelet[15046]: E0323 12:54:57.324647   15046 kubelet.go:1468] "Image garbage collection failed once. Stats initialization may not have completed yet" err="invalid capacity 0 on image filesystem"
Mar 23 12:54:57 kubeception-544bdb89f9-mxt9t kubelet[15046]: E0323 12:54:57.339994   15046 kubelet.go:2380] "Skipping pod synchronization" err="[container runtime status check may not have completed yet, PLEG is not healthy: pleg has yet to be successful]"
Mar 23 12:54:57 kubeception-544bdb89f9-mxt9t kubelet[15046]: E0323 12:54:57.440345   15046 kubelet.go:2380] "Skipping pod synchronization" err="container runtime status check may not have completed yet"
# journalctl -u containerd | grep error
Mar 23 12:56:50 kubeception-544bdb89f9-mxt9t containerd[17174]: time="2025-03-23T12:56:50.268117621Z" level=info msg="skip loading plugin" error="no scratch file generator: skip plugin" id=io.containerd.snapshotter.v1.blockfile type=io.containerd.snapshotter.v1
Mar 23 12:56:50 kubeception-544bdb89f9-mxt9t containerd[17174]: time="2025-03-23T12:56:50.271726631Z" level=warning msg="Ignoring unknown key in TOML for plugin" error="strict mode: fields in the document are missing in the target struct" key=tolerate_missing_hugepages_controller plugin=io.containerd.cri.v1.runtime
Mar 23 12:56:50 kubeception-544bdb89f9-mxt9t containerd[17174]: time="2025-03-23T12:56:50.279568281Z" level=info msg="skip loading plugin" error="skip plugin: tracing endpoint not configured" id=io.containerd.tracing.processor.v1.otlp type=io.containerd.tracing.processor.v1
Mar 23 12:56:50 kubeception-544bdb89f9-mxt9t containerd[17174]: time="2025-03-23T12:56:50.279621471Z" level=info msg="skip loading plugin" error="skip plugin: tracing endpoint not configured" id=io.containerd.internal.v1.tracing type=io.containerd.internal.v1
Mar 23 12:56:50 kubeception-544bdb89f9-mxt9t containerd[17174]: time="2025-03-23T12:56:50.280767571Z" level=error msg="failed to load cni during init, please check CRI plugin status before setting up network for pods" error="cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config"
문서 댓글 ({{ doc_comments.length }})
{{ comment.name }} {{ comment.created | snstime }}