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
Copy file name to clipboardExpand all lines: README.md
+81-79
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@
8
8
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
9
Some basic familiarity with Docker and the [Docker Command Line](https://docs.docker.com/engine/reference/commandline/cli/) is assumed.
10
10
11
+
**Note**: In version 1.2 we removed the named VOLUME from the build. It should not affect many users - but the details are [here](volumechanges).
12
+
11
13
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
14
13
15
Previous 0.20.x versions are still available at https://hub.docker.com/r/nodered/node-red-docker.
@@ -24,25 +26,25 @@ Let's dissect that command:
24
26
-p 1880:1880 - connect local port 1880 to the exposed internal port 1880
25
27
-v node_red_data:/data - mount the host node_red_data directory to the container /data directory so any changes made to flows are persisted
26
28
--name mynodered - give this machine a friendly local name
27
-
nodered/node-red - the image to base it on - currently Node-RED v1.1.3
29
+
nodered/node-red - the image to base it on - currently Node-RED v1.2.0
28
30
29
31
30
32
Running that command should give a terminal window with a running instance of Node-RED.
With the support of Docker manifest list, there is no need to explicitly add the tag for the architecture to use.
184
186
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.
185
187
186
188
Therefore all tags regarding Raspberry PI's are dropped.
187
189
188
-
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.3-10-arm32v7`), and run the container.
190
+
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.2.0-10-arm32v7`), and run the container.
189
191
```
190
192
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:latest
191
193
```
192
194
193
-
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.3-10-amd64`).
195
+
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.2.0-10-amd64`).
194
196
195
197
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.
196
198
197
199
**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:
198
200
```
199
-
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:1.1.3-10-minimal-arm32v6
201
+
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:1.2.0-10-minimal-arm32v6
200
202
201
203
```
202
204
@@ -330,7 +332,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
330
332
The main sections to modify are
331
333
332
334
"dependencies": {
333
-
"node-red": "^1.1.3", <-- set the version of Node-RED here
335
+
"node-red": "^1.2.0", <-- set the version of Node-RED here
334
336
"node-red-dashboard": "*" <-- add any extra npm packages here
335
337
},
336
338
@@ -384,11 +386,11 @@ This tool assumes Node-RED is available at the following address
384
386
385
387
Refreshing the browser page should now reveal the newly added node in the palette.
386
388
387
-
### Node-RED Commands from the host
389
+
### Node-RED Commands from the host
388
390
389
391
Admin commands can also be accessed without installing npm or the
390
392
node-red-admin tool on the host machine. Simply prepend your command
@@ -461,7 +463,7 @@ Then run nodered docker, also added to the same bridge
461
463
462
464
docker run -itd -p 1880:1880 --network iot --name mynodered nodered/node-red
463
465
464
-
containers on the same user-defined bridge can take advantage of the built in name resolution provided by the bridge and use the container name (specified using the **--name** option) as the target hostname.
466
+
containers on the same user-defined bridge can take advantage of the built in name resolution provided by the bridge and use the container name (specified using the **--name** option) as the target hostname.
465
467
466
468
467
469
In the above example the broker can be reached from the Node-RED application using hostname *mybroker*.
@@ -520,7 +522,7 @@ Let's dissect both commands:
520
522
-it - attach a terminal session so we can see what is going on
521
523
-p 1880:1880 - connect local port 1880 to the exposed internal port 1880
522
524
-p 9229:9229 - connect local port 9229 to the exposed internal port 9229 (for debugger communication)
523
-
-v node_red_data:/data - mount the internal /data to the host mode_red_data directory
525
+
-v node_red_data:/data - mount the internal /data to the host mode_red_data directory
524
526
--name mynodered - give this machine a friendly local name
525
527
--entrypoint npm - overwrite the default entrypoint (which would run the *'start'* script)
526
528
nodered/node-red - the image to base it on - currently Node-RED v1.1.0
@@ -530,7 +532,7 @@ Let's dissect both commands:
530
532
531
533
## Common Issues and Hints
532
534
533
-
Here is a list of common issues users have reported with possible solutions.
535
+
Here is a list of common issues users have reported with possible solutions.
534
536
535
537
<br>
536
538
@@ -545,11 +547,11 @@ If you are seeing *permission denied* errors opening files or accessing host dev
0 commit comments