Closed rborkow closed 2 years ago
Did you run the command in the error message (suitably modified to match the path on the host machine)?
Also which Container version are you using?
Yes - I ran the chown command on the docker host (no sudo in the container).
Using the latest
image tag.
Tried with latest-18
, and building a Debian image from scratch with no success.
OK, I was able to fix this by opening a shell in the container as the root user, and running chown -R 1000:1000 "/data/.npm"
.
I met this issues too, when i install contrib , node-red report same error... almost not fixed this error
What are the steps to reproduce?
/data
folder in the docker-compose file.What happens?
I first ran into this error when trying to update packages via the palette browser - all package updates would fail with some version of the below error (nom debug log attached):
Double and triple checked the permissions and they look correct. Tried deleting the .npm folder and node_modules, no change.
Created a new directory and destroyed/recreated the container and I'm still getting the same error. Attempts to
npm install
from the container shell also fail.What do you expect to happen?
Packages to update/install successfully.
Please tell us about your environment:
[ ] Platform/OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-48-generic aarch64)
[ ] Browser: Safari
container.log
npm.log