EACCES: permission denied, open '/data/.config.json' about node-red-docker HOT 5 CLOSED

Thanks for the tips. Removing -v /media/data/node-red/:/data does indeed work.

It turns out that the vfat partition was not writeable by anything other than my user (my user also runs docker). Fixed that (added a umask in /etc/fstab) and Node-RED now starts correctly. Interestingly other container types could write logs etc without issue.

from node-red-docker.

do the permissions on the host side allow that docker user access ?

from node-red-docker.

I'm having trouble replicating your user error locally, using the following command.

docker run -it -p 1880:1880 --restart=always --name="nodered" -v /tmp/node-red/:/data -e FLOWS=flows.json nodered/node-red-docker:rpi

My NR instance starts and is usable without seeing the error you encountered above.

Can you try @dceejay's suggestion about checking the user perms?

We have published an update to the Docker images today that means you don't actually need to use volumes to persist user data. There's more details in the updated README.
If you drop the -v /media/data/node-red/:/data parameters I'm assuming it works?

from node-red-docker.

can anyone share an example of the configuration on the umask entry?

from node-red-docker.

@StuckInLoop my /etc/fstab has the following entry:

UUID=XXXX /media/data vfat auto,nofail,noatime,users,rw,uid=pilot,gid=pilot,umask=000 0 0

You will need to add the UUID of your media in place of XXXX

from node-red-docker.