-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
ImagePull failure - can't unmount tmpmount #10239
Comments
Hey @willthames, are you running some kind of monitoring/security software on your nodes by any chance. If yes, it might be something similar as #5538 |
@Fricounet not as far as I can tell - we do have a few daemonset agents that could theoretically be responsible but none of them mount the host volumes that would be needed to keep the tmpmounts files open. We also don't have anything weird running on the host outside of containers - our production instances are bottlerocket instances using AWS's AMIs
|
Description
We occasionally get ImagePull errors, particularly at node start time, but at other times too.
Steps to reproduce the issue
Describe the results you received and expected
Expected: images that exist and are accessible on other nodes pull on every node
Actual (I've added extra line breaks so that the output is readable):
I've tried straceing this but all I see is
EBUSY
returned from theumount2
system call. I can't find any candidates for the mount being used elsewhere - I've looked for candidate processes similar to fluent from #9530 but we don't seem to hostPath mount /var/lib or /var/lib/containerd anywhere.What version of containerd are you using?
containerd github.com/containerd/containerd 1.6.31+bottlerocket e377cd5
Any other relevant information
Show configuration if it is related to CRI plugin.
The text was updated successfully, but these errors were encountered: