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

Installation Failed - Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock' #501

Open
Ccheese4 opened this issue Nov 17, 2022 · 0 comments

Comments

@Ccheese4
Copy link

Describe the Problem
I am having difficulty getting this module to install. I get the following output to the log file within NodeRed:

2022-11-17T20:59:00.574Z Install : node-red-contrib-sun-position 2.1.1

2022-11-17T20:59:00.743Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-11-17T20:59:04.160Z [err] npm
2022-11-17T20:59:04.160Z [err]  WARN locking Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'
2022-11-17T20:59:04.160Z [err] npm WARN locking  /data/.npm/_locks/staging-accc372ed0ccb0d8.lock failed [Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'] {
2022-11-17T20:59:04.160Z [err] npm WARN locking   errno: -13,
2022-11-17T20:59:04.160Z [err] npm WARN locking   code: 'EACCES',
2022-11-17T20:59:04.160Z [err] npm WARN locking   syscall: 'open',
2022-11-17T20:59:04.160Z [err] npm WARN locking   path: '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'
2022-11-17T20:59:04.160Z [err] npm WARN locking }
2022-11-17T20:59:04.205Z [err] npm ERR! 
2022-11-17T20:59:04.205Z [err] code EACCES
2022-11-17T20:59:04.205Z [err] npm ERR! syscall open
2022-11-17T20:59:04.205Z [err] npm ERR! path /data/.npm/_locks/staging-accc372ed0ccb0d8.lock
2022-11-17T20:59:04.205Z [err] npm ERR! errno -13
2022-11-17T20:59:04.206Z [err] npm ERR! 
2022-11-17T20:59:04.206Z [err] npm 
2022-11-17T20:59:04.206Z [err] ERR! Your cache folder contains root-owned files, due to a bug in
2022-11-17T20:59:04.206Z [err] npm ERR! previous versions of npm which has since been addressed.
2022-11-17T20:59:04.206Z [err] npm ERR! 
2022-11-17T20:59:04.206Z [err] npm ERR! To permanently fix this problem, please run:
2022-11-17T20:59:04.206Z [err] npm ERR!
2022-11-17T20:59:04.207Z [err]    sudo chown -R 1000:1000 "/data/.npm"
2022-11-17T20:59:04.217Z [err] 
2022-11-17T20:59:04.217Z [err] npm ERR! A complete log of this run can be found in:
2022-11-17T20:59:04.217Z [err] npm ERR!     /data/.npm/_logs/2022-11-17T20_59_04_207Z-debug.log
2022-11-17T20:59:04.223Z rc=243

I am running NodeRed as a docker on my Unraid server. Home Assistant is running as a VM.

I have attempted to run the sudo chown -R 1000:1000 "/data/.npm" command recommended in the log file with no success. I attempted to run it from the Unraid NodeRed docker console, and got sh: sudo: not found. If I run it without sudo, I get chown: /data/.npm/_locks: Operation not permitted.

Expected behavior
I expected the module to install. I have not had issues installing a limited handful of modules before. I did not find anything about this in the Installation portion of the flows.nodered.org page.

System information

  • Node-Red Version 2.0.0-beta.1
  • Unraid Version 6.11.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant