Permission denied missing write access to /opt/app/node_modules

Following the instructions from the README, I cannot install additional Node packages with docker-compose exec node npm install --save <package name> due to write permissions of the ‘node’ user. If I update docker-compose.yml to set the user as ‘root’, I can again install pacakges. I’m not sure if this is the best way to solve the install permissions or not.

[BretFisher]

A few options to solve this depending on what you’d like to do, in order of my preference (feedback welcome!):

1. Fix the permissions on node_modules so they are all installed as node user, which means moving the USER Dockerfile stanza up to before npm install. This keeps your dev and prod permissions the same without reducing security (node_modules are typically the same permissions as your app files anyway.) I like this idea so much I’m going to update the repo to use this method by default, which requires moving node_modules down a directory to ensure npm has permissions to write to the pwd of node_modules. I’ll close this issue with that commit but feel free to keep commenting.
2. Run your exec commands as root using -u root and specify the working directory to the proper /opt with: docker-compose exec -u root -w /opt/ node npm install --save <package name>
3. Update docker-compose.yml with the user:root key to run the CMD as root for local development. I now like the above two options better.

[nielsbril]

Dependencies can be installed again, but I still get the EBUSY: resource busy or locked error on package.json and package-lock.json due to the bind mount. Is there any way to fix this?

I’m on macOS 10.14.3 with Docker 18.09.2 and Docker Compose 1.23.2.