raphcalvignac/rpi-nodered repository overview

⁠rpi-nodered

Docker image for nodered adapted to Rpi based on official nodered/node-red-docker image with additional modbus nodes (source: https://hub.docker.com/r/nodered/node-red-docker/⁠)

⁠Run

docker run -it -p 1880:1880 --name nodered raphcalvignac/rpi-nodered:0.2

Browse http://{host_ip}:1880 to get the Node-RED desktop.

⁠Adding Nodes

Manually add nodes to the container

docker exec –it nodered /bin/bash (access to container bash)
cd /data
export http_proxy= ...
export https_proxy= ...
npm install node-red-contrib-modbustcp (modbus node here as exemple)
exit (return to host)
docker stop nodered
docker start nodered

⁠Save changes in custom image

Modifications to files within the live container, e.g. manually adding nodes or creating flows, do not exist outside the lifetime of the container.

Docker allows you to save the current state of a container to a new image. This means you can persist your changes as a new image that can be shared on other systems.

docker commit nodered custom-node-red-docker

⁠Run with data persistence

Node-RED uses the /data directory to store user configuration data. Use of a named data volume to persist the user configuration: Create volume:

docker volume create --name nodered-data

Run container with persistent data:

docker run -it -p 1880:1880 -v nodered-data:/data --name nodered raphcalvignac/rpi-nodered:0.2