npm install doesn’t fail, or fails for non i/o related reasons.
13162 verbose stack Error: EIO: i/o error, open '/home/build/.npm/request/2.33.0/package/package.json' 13162 verbose stack at Error (native) 13163 verbose cwd /work 13164 error Linux 4.4.13-moby 13165 error argv "/work/node/node" "/work/node/node_modules/npm/bin/npm-cli.js" "install" "--progress=false" "--no-bin-links" "--no-shrinkwrap" 13166 error node v4.4.5 13167 error npm v3.9.5 13168 error path /home/build/.npm/request/2.33.0/package/package.json 13169 error code EIO 13170 error errno -5 13171 error syscall open 13172 error EIO: i/o error, open '/home/build/.npm/request/2.33.0/package/package.json' 13173 error If you need help, you may report this error at: 13173 error <https://github.com/npm/npm/issues> 13174 verbose exit [ -5, true ]
(Plus many more similar errors in the log file)
Win 10 Pro.
docker version: Client: Version: 1.12.0-rc2 API version: 1.24 Go version: go1.6.2 Git commit: 906eacd Built: Fri Jun 17 20:35:33 2016 OS/Arch: windows/amd64 Experimental: true Server: Version: 1.12.0-rc2 API version: 1.24 Go version: go1.6.2 Git commit: a7119de Built: Fri Jun 17 22:09:20 2016 OS/Arch: linux/amd64 Experimental: true
Junos Pulse VPN connection (I have to disable/reenable DockerNAT every time I reconnect the vpn, but after I do this everything seems to work)
Diagnostic ID: 216B30D2-4FB5-4DED-88DC-F7EE126956B7/2016-06-24_09-27-34
looking at the output of “dmesg” on the mobylinux system I believe this message is related:
[ 70.758106] CIFS VFS: SMB signature verification returned error = -13
There are dozens of these lines, along with a few of these:
[ 561.521536] cifs_vfs_err: 18 callbacks suppressed
I am mounting the NPM cache directory at /usr/.npm
and symlinking that to the home directory of the build user
ln -s /usr/.npm /home/build/.npm
I have tried mounting the npm cache directory directly to the /home/build/.npm directory as well and the same issue occurs.
I tried remounting the cifs shares with some other options, such as
vers=3.02,cache=none but even after remounting the shares and restarting the container the mount command inside the container didn’t show that the mount options had changed.