EPERM: operation not permitted, scandir

Hi,

Trying to run a Node app in a Docker image based on mhart/alpine-node:6.4.0, I get the following stack trace which points to Glob:

/node_modules/webdriverio/build/lib/cli.js:369
            throw e;
            ^

Error: EPERM: operation not permitted, scandir '/proc/1/map_files/561b222d4000-561b23a8b000'
    at Error (native)
    at Object.fs.readdirSync (fs.js:951:18)
    at GlobSync._readdir (/node_modules/glob/sync.js:276:41)
    at GlobSync._readdirInGlobStar (/node_modules/glob/sync.js:255:20)
    at GlobSync._readdir (/node_modules/glob/sync.js:264:17)
    at GlobSync._processReaddir (/node_modules/glob/sync.js:136:22)
    at GlobSync._process (/node_modules/glob/sync.js:131:10)
    at GlobSync._processGlobStar (/node_modules/glob/sync.js:368:10)
    at GlobSync._process (/node_modules/glob/sync.js:129:10)
    at GlobSync._processGlobStar (/node_modules/glob/sync.js:371:10)

Is this a bug, and/or is there any known workaround? It occurs also when run as root. Thanks!

Issue Analytics

State:
Created 7 years ago
Reactions:12
Comments:11 (1 by maintainers)

Top GitHub Comments

2reactions

ghostcommented, Jul 11, 2017

Is there a “continue on error”? strict: false worked for me.

1reaction

spemmonscommented, Apr 27, 2017

i created a fork and modified the sync.js to treat EPERM errors the same as ENOENT and was able to continue successfully… this would seem to be the same situation (in my case) a trying to do a recursive list of files where you don’t have permission for some nested subdirectories… perhaps one could argue that handling for this could be based on an option, but i’m not sure that’s really necessary… is this an active project that i could submit a pull request to? it unfortunately looks pretty stale…