Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AL2023 AMI: "invalid capacity 0 on image filesystem" kubelet warning #1947

Closed
markusmiliats opened this issue Sep 2, 2024 · 1 comment
Closed

Comments

@markusmiliats
Copy link

markusmiliats commented Sep 2, 2024

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 Region: eu-central-1
  • Instance Type(s): r5a.xlarge
  • EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.17
  • Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.28
  • AMI Version: AL2023 1.28.11-20240828 and 1.28.11-20240817
  • Kernel (e.g. uname -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
  • Release information (run cat /etc/eks/release on a node):
BASE_AMI_ID="ami-0ba8fabdb90841bee"
BUILD_TIME="Wed Aug 28 01:53:55 UTC 2024"
BUILD_KERNEL="6.1.102-111.182.amzn2023.x86_64"
ARCH="x86_64"
@cartermckinnon
Copy link
Member

You can ignore it.

@cartermckinnon cartermckinnon closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants