too many open files

[oursland]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Continue operating software that worked in Docker Desktop for Mac v4.2.0

Actual behavior

Several systems failed with errors indicating "too many open files".

Information

• macOS Version: 12.0.1 Monterey
• Intel chip or Apple chip: Intel
• Docker Desktop Version: 4.3.0

Steps to reproduce the behavior

This error was present with my use of node application with file watching as well as through kubernetes tooling (i.e. prometheus).

The error was resolved by rolling back to v4.2.0.

[StefanScherer]

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]

Could you upload diagnostics, please? See https://docs.docker.com/desktop/mac/troubleshoot/#diagnose-and-feedback

[djs55]

Just in case the diagnostics fails (because of too many open files), could you try

lsof -Pn

This should list all the open files making it easier to spot where the leak is.

[yunussandikci]

I am having the same issue with M1 CPUs when I create a Kind cluster with about 40 pods.

[oursland]

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]

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]

cc @thaJeztah

[StefanScherer]

We've released Docker Desktop 4.5.0 which fixes this issue.

[killianmuldoon]

Thanks @StefanScherer this is working for me 😄

[moisesrodriguez]

@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

[docker-robott]

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