You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project describes some of the many ways Node-RED can be run under Docker and has support for multiple architectures (amd64, arm32v6, arm32v7, arm64v8, i386 and s390x).
9
-
Some basic familiarity with Docker and the [Docker Command Line](https://docs.docker.com/engine/reference/commandline/cli/) is assumed.
9
+
Some basic familiarity with Docker and the [Docker Command Line](https://docs.docker.com/engine/reference/commandline/cli/) is assumed.
10
10
11
11
As of Node-RED 1.0 this project provides the build for the `nodered/node-red` container on [Docker Hub](https://hub.docker.com/r/nodered/node-red/).
12
12
@@ -23,15 +23,15 @@ Let's dissect that command:
23
23
-it - attach a terminal session so we can see what is going on
24
24
-p 1880:1880 - connect local port 1880 to the exposed internal port 1880
25
25
--name mynodered - give this machine a friendly local name
26
-
nodered/node-red - the image to base it on - currently Node-RED v1.0.6
26
+
nodered/node-red - the image to base it on - currently Node-RED v1.1.0
27
27
28
28
29
29
Running that command should give a terminal window with a running instance of Node-RED.
30
30
31
31
Welcome to Node-RED
32
32
===================
33
33
34
-
03 Oct 12:57:10 - [info] Node-RED version: v1.0.6
34
+
03 Oct 12:57:10 - [info] Node-RED version: v1.1.0
35
35
03 Oct 12:57:10 - [info] Node.js version: v10.16.3
36
36
03 Oct 12:57:10 - [info] Linux 4.9.184-linuxkit x64 LE
37
37
03 Oct 12:57:11 - [info] Loading palette nodes
@@ -109,36 +109,36 @@ The following table shows the variety of provided Node-RED images.
With the support of Docker manifest list, there is no need to explicitly add the tag for the architecture to use.
181
181
When a docker run command or docker service command or docker stack command is executed, docker checks which architecture is required and verifies if it is available in the docker repository. If it does, docker pulls the matching image for it.
182
182
183
183
Therefore all tags regarding Raspberry PI's are dropped.
184
184
185
-
For example: suppose you are running on a Raspberry PI 3B, which has `arm32v7` as architecture. Then just run the following command to pull the image (tagged by `1.0.6-10-arm32v7`), and run the container.
185
+
For example: suppose you are running on a Raspberry PI 3B, which has `arm32v7` as architecture. Then just run the following command to pull the image (tagged by `1.1.0-10-arm32v7`), and run the container.
186
186
```
187
187
docker run -it -p 1880:1880 --name mynodered nodered/node-red:latest
188
188
```
189
189
190
-
The same command can be used for running on an amd64 system, since docker discovers its running on a amd64 host and pulls the image with the matching tag (`1.0.6-10-amd64`).
190
+
The same command can be used for running on an amd64 system, since docker discovers its running on a amd64 host and pulls the image with the matching tag (`1.1.0-10-amd64`).
191
191
192
192
This gives the advantage that you don't need to know/specify which architecture you are running on and makes docker run commands and docker compose files more flexible and exchangeable across systems.
193
193
194
194
**Note**: Currently there is a bug in Docker's architecture detection that fails for `arm32v6` - eg Raspberry Pi Zero or 1. For these devices you currently need to specify the full image tag, for example:
195
195
```
196
-
docker run -it -p 1880:1880 --name mynodered nodered/node-red:1.0.6-10-minimal-arm32v6
196
+
docker run -it -p 1880:1880 --name mynodered nodered/node-red:1.1.0-10-minimal-arm32v6
197
197
```
198
198
199
199
## Raspberry PI - native GPIO support
@@ -324,7 +324,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
324
324
The main sections to modify are
325
325
326
326
"dependencies": {
327
-
"node-red": "^1.0.6", <-- set the version of Node-RED here
327
+
"node-red": "^1.1.0", <-- set the version of Node-RED here
328
328
"node-red-dashboard": "*" <-- add any extra npm packages here
329
329
},
330
330
@@ -488,7 +488,7 @@ Sometimes it is useful to debug the code which is running inside the container.
488
488
docker run -it -p 1880:1880 -p 9229:9229 --name mynodered --entrypoint npm nodered/node-red run debug_brk -- --userDir /data
489
489
```
490
490
Note that in this case NodeJs will wait - at the first statement of the Node-RED application - until a debugger client connects...
491
-
491
+
492
492
As soon as NodeJs is listening to the debug port, this will be shown in the startup log:
0 commit comments