-
Notifications
You must be signed in to change notification settings - Fork 715
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
Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data for container / #1025
Comments
I think it's ok to ignore that error. Are those messages from before kubeadm init is run? Does the error persist after kubeadm init succeeds? |
kubelet runonce can't start static pod.. |
I also met with the same issue: "Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data for container /" |
does this problem have serious influence?I met this today and some other problem which together lead to that I can not stop certain container and some pod hang on Terminating status. The following is the scene
|
Have the same issue and the node where it happens went into NotReady state:
Running 1.18.0 |
I see the same error followed by |
you might want to search for the same error message reported in the kubernetes/kubernetes repository and if there is no ticket for that - create one and mark it with |
We have the same error. |
I have the same error.kubeadm init failed because of a kubelet failure. Kubernetes v1.18.1 |
Has your problem been solved? I have the same problem. |
i have same error |
hi, ppl! do you find a solution for this? thanks |
Finally, I solved it by re-installing containerd |
and i hava the internet ,
docker images
I don't know why it looks like this. Everything looks normal.
The text was updated successfully, but these errors were encountered: