Closed Moon-developer closed 1 year ago
that's weird, it seems a permissions issue, you could try to run inside the docker container sudo chown -R 1000:1000 "/root/.npm"
as it is suggested from npm, or add this command into the Dockerfile of docker-ac-eluna-ts-dev
I was able to replicate this with a root-owned scripts
directory.
To fix this, you should make the /path/to/acore-docker/scripts
directory accessible by the 1000
user. Either command chown -R 1000:1000 ./scripts
or chmod -R 777 ./scripts
should work here.
If you still have the override suggested in https://github.com/azerothcore/acore-docker/issues/14#issuecomment-1411643547, you can remove that.
Thank you, will try this later today and report back here.
I followed a suggestion to fix one of the containers not starting due to
index
permission. But I'm noticing that theacore-docker-ac-eluna-ts-dev-1
container is spitting out the following error now:Any idea how to fix this? It seems to be a directory in the container but I can't access it when it's in a
restart
loop.