Open sorenjohanson opened 1 week ago
This is most likely caused by (accidentally) overwriting node_modules created by the Dockerfile in docker-compose.yml
:
volumes:
- .:/home/node/app
- ./node_modules:/home/node/app/node_modules:cached
With a fresh clone of the repository and when executing
docker compose up -d
for the first time,node_modules
seems to be created withroot:root
permissions. This preventsyarn install
from executing successfully as it's run with thenode
user.Not sure if this is a local issue, but once
node_modules
is created in the local file system, it's possible to work around the issue by setting the correct permissions locally (in my case,cert:cert
) and forcibly re-creating the Docker container usingdocker compose up -d --build --force-recreate
. Thenode_modules
folder is then created/copied with the correct permissions.