-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add FAQ entry about too many open files
errors when using a container-based driver
#20168
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: EmmanuelKasper The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @EmmanuelKasper! |
Hi @EmmanuelKasper. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Can one of the admins verify this patch? |
d28c070
to
5db8f1e
Compare
too many open files errors
when using a container-based drivertoo many open files
errors when using a container-based driver
This is based on https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files and was also mentioned in https://00formicapunk00.wordpress.com/2024/12/10/too-many-open-files-in-minikube-pod/
The problem will pop up on HA setups using a container driver. I had this with Docker, but probably Podman will hit the same limit, as this is a Linux kernel limit independant of the container runtime.