jamesbrink/node-red repository overview

⁠Docker Container for Node-RED

This is a Docker container for Node-RED⁠. The Goal of this container is to create a customizable yet easy to use instance of Node-RED while maintaining a small footprint.

⁠Usage

To run with default settings:

docker run -P jamesbrink/node-red

This will run Node-RED exposing it on a randomly generated TCP port.

For example, I can run docker ps and see my container started up and mapped the exposed port for Node-RED to 32770.

mbp:~$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS              PORTS                     NAMES
a5de1eac9387        node-red            "/usr/bin/node-red --"   About a minute ago   Up About a minute   0.0.0.0:32770->1880/tcp   stupefied_roentgen

Because I am running using docker-machine⁠, I need to also obtain the virtual machine's IP address to access Node-RED.

mbp:~$ docker-machine ip docker
192.168.32.145

A quick curl to the docker-machine IP address and we can see a response from the container

mbp:~$ curl -I 192.168.32.145:32770
HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/html; charset=utf-8
Content-Length: 8300
ETag: W/"206c-owtn/uuHF9+H9sd4KcnyVQ"
Date: Sun, 01 May 2016 01:13:17 GMT
Connection: keep-alive

I have included a basic docker-compose.yml⁠ which creates a basic named Volume⁠ to persist Node-RED configuration and Flows

docker-compose up

⁠Data Volumes

The following directories are setup as volumes. For detailed information on Data Volumes⁠ please refer to the official Docker Documentation⁠.

• /data - Node-RED configuration data and Flows reside.

The /data volume contains your Node-RED configuration settings, as well as your Flows. You will want to use this volume to persist your data during upgrades or the share with other containers.