Bad file descriptor after updating to 1.11.1-beta13

@lassebm what version are you running? The EBADF issue should have been fixed in Beta13.1 but the ENOENT report by @nuck is new and has not been reproduced.

@dsheets -beta14 from today.

@lassebm I have reproduced and traced the issue. The root cause is a race between release of file handles and their non-atomic use for metadata operations. I have filed internal issue #3683 to track this defect.

I’m sorry that this defect is causing you issues. We’ve given it high priority and hope to have a fix out later this week.

Thanks for your report and for participating in the Docker for Mac Beta!

@dsheets Great news! Thanks a lot for your quick tracing and prioritization.

Hey @dsheets,

Thanks for looking into this. I wanted to note that this error is still occurring for me on Beta 15 as well.

Steps to Reproduce:

  • Clone a node.js based project that is setup for Docker. For example, https://bitbucket.org/modusoperandi/backbone-marionette-es6-seed
  • Run the npm install command. In the example above, this is done by default with docker-compose up
  • Notice how it fails to execute with a npm ERR! EBADF: bad file descriptor error.
  • rm -rf node_modules between runs to verify if this is working as expected.

The above steps work as expected with the latest version of docker-toolbox.

Can confirm, still reproducible in -beta15.

@dsheets Could you let us know what build this issue was fixed in? (I’m seeing a bad file descriptor on Version 18.03.1-ce-mac65 (24312) I was wondering if I need to update to the latest beta).
Thanks.