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
I'm not sure if this is a bug so I'm filing this as a general question.
During node startup I can see the event "invalid capacity 0 on image filesystem" as a warning from kubelet.
Using journalctl -u kubelet I can see additional information for this warning: kubelet.go:1440] "Image garbage collection failed once. Stats initialization may not have completed yet" err="invalid capacity 0 on image filesystem"
Afterwards, the node starts normally, pods are assigned to the node and I cannot observe any abnormal behaviour.
I'm wondering if anyone else encountered this and if I can safely ignore this warning? (because Stats initialization may not have completed yet as the message already suggests 😄)
I'm not sure if this is a bug so I'm filing this as a general question.
During node startup I can see the event "invalid capacity 0 on image filesystem" as a warning from kubelet.
Using
journalctl -u kubelet
I can see additional information for this warning:kubelet.go:1440] "Image garbage collection failed once. Stats initialization may not have completed yet" err="invalid capacity 0 on image filesystem"
Afterwards, the node starts normally, pods are assigned to the node and I cannot observe any abnormal behaviour.
I'm wondering if anyone else encountered this and if I can safely ignore this warning? (because Stats initialization may not have completed yet as the message already suggests 😄)
Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
): eks.17aws eks describe-cluster --name <name> --query cluster.version
): 1.28uname -a
):Linux ip-10-156-75-203.eu-central-1.compute.internal 6.1.102-111.182.amzn2023.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Aug 13 22:23:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/eks/release
on a node):The text was updated successfully, but these errors were encountered: