I'm sure this is a simple question stemming from my lack of Unix literacy. Installed NR in docker on Synology NAS. I needed flow/module data to persist outside docker, so used a volume mapping to the main filesystem. To get this to work (ie get rid of the permissions errors on startup) I needed to change the permissions on the target location to give everyone full permissions (yes I know, a bad idea, but temporary to work out what is going on). NR now comes up and functions as expected. Files in the mounted volume are created as expected and have user/group of 1001,1001. Looking at the dockerfile, this appears to be the result of docker creating a "node-red" user inside the container. Since there does not appear to be any control over uid/gid in the user creation machinery in DSM, not sure how to sync the internal user with an external user that would allow me to lock this down. Any thoughts? I am presuming that changing/removing the user creation code in the dockerfile might work...
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Docker on Synology | 4 | 2337 | 30 June 2020 | |
Node-Red-Docker on Synology NAS; How do secure Node-Red | 12 | 5589 | 22 July 2020 | |
How to access config file when using in docker (synology)? | 7 | 4869 | 2 December 2020 | |
Node Red Docker on Synology Connection problem | 3 | 320 | 19 December 2022 | |
Node RED on Synology Docker - acces rights | 2 | 952 | 20 February 2021 |