ci icon indicating copy to clipboard operation
ci copied to clipboard

Error running npm install in github-action/: "ENOTDIR: not a directory, open '/workspaces/devcontainer-build-run/github-action/node_modules/devcontainer-build-run-common/npm-shrinkwrap.json'"

Open jjliggett opened this issue 2 years ago • 2 comments

I am encountering an error when running npm install in the directory github-action, in the Dev Container:

vscode ➜ /workspaces/devcontainer-build-run (feat/support-giving-extended-privileges-to-container ✗) $ cd github-action/ vscode ➜ /workspaces/devcontainer-build-run/github-action (feat/support-giving-extended-privileges-to-container ✗) $ ls dist jest.config.js lib Makefile node_modules package.json package-lock.json src tsconfig.json vscode ➜ /workspaces/devcontainer-build-run/github-action (feat/support-giving-extended-privileges-to-container ✗) $ npm install npm ERR! code ENOTDIR npm ERR! syscall open npm ERR! path /workspaces/devcontainer-build-run/github-action/node_modules/devcontainer-build-run-common/npm-shrinkwrap.json npm ERR! errno -20 npm ERR! ENOTDIR: not a directory, open '/workspaces/devcontainer-build-run/github-action/node_modules/devcontainer-build-run-common/npm-shrinkwrap.json'

npm ERR! A complete log of this run can be found in: npm ERR! /home/vscode/.npm/_logs/2021-08-29T18_04_58_314Z-debug.log

vscode ➜ /workspaces/devcontainer-build-run/github-action (feat/support-giving-extended-privileges-to-container ✗) $ vi /home/vscode/.npm/_logs/2021-08-29T18_04_58_314Z-debug.log

0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'install' ] 2 info using [email protected] 3 info using [email protected] 4 verbose npm-session 707288085a93a29d 5 silly install runPreinstallTopLevelLifecycles 6 silly preinstall [email protected] 7 info lifecycle [email protected]~preinstall: [email protected] 8 silly install loadCurrentTree 9 silly install readLocalPackageData 10 timing stage:loadCurrentTree Completed in 1740ms 11 silly install loadIdealTree 12 silly install cloneCurrentTreeToIdealTree 13 timing stage:loadIdealTree:cloneCurrentTree Completed in 14ms 14 silly install loadShrinkwrap 15 timing stage:loadIdealTree:loadShrinkwrap Completed in 629ms 16 silly install loadAllDepsIntoIdealTree 17 timing stage:rollbackFailedOptional Completed in 0ms 18 timing stage:runTopLevelLifecycles Completed in 2409ms 19 silly saveTree [email protected] 19 silly saveTree ├── @actions/[email protected] ... 19 silly saveTree ├─┬ [email protected] 19 silly saveTree │ ├── [email protected] 19 silly saveTree │ ├── [email protected] 19 silly saveTree │ ├── [email protected] 19 silly saveTree │ ├── [email protected] 19 silly saveTree │ └── [email protected] 19 silly saveTree └── [email protected] 20 verbose stack Error: ENOTDIR: not a directory, open '/workspaces/devcontainer-build-run/github-action/node_modules/devcontainer-build-run-common/npm-shrinkwrap.json' 21 verbose cwd /workspaces/devcontainer-build-run/github-action 22 verbose Linux 5.4.72-microsoft-standard-WSL2 23 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" 24 verbose node v12.22.5 25 verbose npm v6.14.14 26 error code ENOTDIR 27 error syscall open 28 error path /workspaces/devcontainer-build-run/github-action/node_modules/devcontainer-build-run-common/npm-shrinkwrap.json 29 error errno -20 30 error ENOTDIR: not a directory, open '/workspaces/devcontainer-build-run/github-action/node_modules/devcontainer-build-run-common/npm-shrinkwrap.json' 31 verbose exit [ -20, true ]

jjliggett avatar Aug 29 '21 18:08 jjliggett

@jjliggett - apologies for the delay on this. Embarrassingly, I missed it among the other issues I'd created and spotted during some housekeeping :-(

Is this related to #100?

stuartleeks avatar May 31 '22 09:05 stuartleeks

@stuartleeks, it's all good, thanks!

I ran into this issue around the same time as that pull request, but this is a different issue.

I encountered this issue after implementing the change in #100 when working on a change to enable dev containers configured with docker-in-docker (commit here). I haven't been able to resolve this issue, but the docker-in-docker support ended up not being a high priority addition to me

jjliggett avatar Jun 01 '22 03:06 jjliggett