Docker volume mapped /data volume uses irritating UID/GID about node-red-docker HOT 6 CLOSED

I stumbled upon this while looking for close matches to #109, so here's a docker-compose snippet that matches the current user by using the UID environment variable:

node-red:
        hostname: flows
        image: "nodered/node-red-docker:0.20.5-slim-v10" # https://hub.docker.com/r/nodered/node-red-docker/tags
        restart: always
        user: ${UID} # this needs to be set so that node-red can match filesystem UIDs
        volumes:
            - /etc/localtime:/etc/localtime:ro
            - /dev/rtc:/dev/rtc:ro
            - ${HOME}/.config/node-red:/data
        ports:
           - "1880:1880"

Hope it's useful.

from node-red-docker.

Sure, you can run docker run -u UID, for example zero for root

from node-red-docker.

Is there someway to do this with docker compose?

from node-red-docker.

@AnderssonPeter, yes, you can add a user line in the instance in the docker-compose file: https://medium.com/redbubble/running-a-docker-container-as-a-non-root-user-7d2e00f8ee15

from node-red-docker.

I also had to add the user for NodeRED before I could start nodered on my raspberry pi but a different issue then occurs when I try to install packages:

Unhandled rejection Error: EACCES: permission denied, mkdir '/.npm'

as .npm is a local folder inside the container nodered shouldn't have any issues creating it right?

edit: trying to sudo the folder via shell gives me the error:
sudo: unknown uid 1001: who are you?

temp solution:
#70 (comment)

remove the user from docker-compose and chmod your local data folder to 777

from node-red-docker.

Node-RED 1.0.0 is now available on docker hub - https://hub.docker.com/r/nodered/node-red.

This closes this issue.

There are a few changes to the new release, please read the README for further details.

from node-red-docker.