Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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'" #101

Open
jjliggett opened this issue Aug 29, 2021 · 2 comments

Comments

@jjliggett
Copy link
Contributor

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 npm@6.14.14
3 info using node@v12.22.5
4 verbose npm-session 707288085a93a29d
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall devcontainer-build-run@0.0.0
7 info lifecycle devcontainer-build-run@0.0.0~preinstall: devcontainer-build-run@0.0.0
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 devcontainer-build-run@0.0.0
19 silly saveTree ├── @actions/core@1.4.0
...
19 silly saveTree ├─┬ ts-jest@26.5.6
19 silly saveTree │ ├── bs-logger@0.2.6
19 silly saveTree │ ├── make-error@1.3.6
19 silly saveTree │ ├── mkdirp@1.0.4
19 silly saveTree │ ├── semver@7.3.5
19 silly saveTree │ └── yargs-parser@20.2.7
19 silly saveTree └── typescript@4.3.2
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 ]

@stuartleeks
Copy link
Collaborator

@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?

@jjliggett
Copy link
Contributor Author

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants