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
Thanks for the report. Do you have more precise repro steps, maybe a sample project on GitHub or compose file etc. to reproduce the problem? We haven't seen this error in our CI.
Just fyi, looks like we have the same issue when running kind and a few more containers. (kubernetes-sigs/cluster-api#5940). I think it probably also occurs when running a few kind clusters.
@StefanScherer I still have the issue with 4.5.0, I get bunch of Error: EIO: i/o error, open errors and eventually too many open files error. I too have file watching for my node app. Reverted to 4.2.0
Activity
StefanScherer commentedon Dec 3, 2021
Thanks for the report. Do you have more precise repro steps, maybe a sample project on GitHub or compose file etc. to reproduce the problem? We haven't seen this error in our CI.
mat007 commentedon Dec 3, 2021
Could you upload diagnostics, please? See https://docs.docker.com/desktop/mac/troubleshoot/#diagnose-and-feedback
djs55 commentedon Dec 3, 2021
Just in case the diagnostics fails (because of too many open files), could you try
This should list all the open files making it easier to spot where the leak is.
yunussandikci commentedon Dec 28, 2021
I am having the same issue with M1 CPUs when I create a Kind cluster with about 40 pods.
oursland commentedon Dec 29, 2021
I encounter this issue when deploying a k3d cluster with a similar number of pods including a live-reloading NodeJS application with many open files.
Again, this issue is not present in previous releases. I believe it to be a misconfiguration of the VM's Linux kernel.
sbueringer commentedon Jan 14, 2022
Just fyi, looks like we have the same issue when running kind and a few more containers. (kubernetes-sigs/cluster-api#5940). I think it probably also occurs when running a few kind clusters.
@killianmuldoon posted a workaround on our issue: kubernetes-sigs/cluster-api#5940 (comment)
dims commentedon Jan 18, 2022
cc @thaJeztah
StefanScherer commentedon Feb 11, 2022
We've released Docker Desktop 4.5.0 which fixes this issue.
killianmuldoon commentedon Feb 11, 2022
Thanks @StefanScherer this is working for me 😄
moisesrodriguez commentedon Feb 23, 2022
@StefanScherer I still have the issue with 4.5.0, I get bunch of
Error: EIO: i/o error, openerrors and eventually too many open files error. I too have file watching for my node app. Reverted to 4.2.0docker-robott commentedon Mar 25, 2022
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked