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
+41-50Lines changed: 41 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,15 +22,15 @@ Let's dissect that command:
22
22
-it - attach a terminal session so we can see what is going on
23
23
-p 1880:1880 - connect local port 1880 to the exposed internal port 1880
24
24
--name mynodered - give this machine a friendly local name
25
-
nodered/node-red - the image to base it on - currently Node-RED v1.0.1
25
+
nodered/node-red - the image to base it on - currently Node-RED v1.0.2
26
26
27
27
28
28
Running that command should give a terminal window with a running instance of Node-RED.
29
29
30
30
Welcome to Node-RED
31
31
===================
32
32
33
-
03 Oct 12:57:10 - [info] Node-RED version: v1.0.1
33
+
03 Oct 12:57:10 - [info] Node-RED version: v1.0.2
34
34
03 Oct 12:57:10 - [info] Node.js version: v10.16.3
35
35
03 Oct 12:57:10 - [info] Linux 4.9.184-linuxkit x64 LE
36
36
03 Oct 12:57:11 - [info] Loading palette nodes
@@ -62,7 +62,7 @@ Running that command should give a terminal window with a running instance of No
62
62
63
63
You can then browse to `http://{host-ip}:1880` to get the familiar Node-RED desktop.
64
64
65
-
**Note**: Currently there is a bug in Docker's architecture detection that fails for Arm6 CPU - eg Raspberry Pi Zero or 1. For these devices you currently need to specify the full build label, for example:
65
+
**Note**: Currently there is a bug in Docker's architecture detection that fails for Arm6 CPU - eg Raspberry Pi Zero or 1. For these devices you currently need to specify the full build label, for example:
66
66
67
67
```
68
68
docker run -it -p 1880:1880 --name mynodered nodered/node-red:1.0.1-10-arm32v6
@@ -113,32 +113,28 @@ 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.
177
169
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.
178
170
179
171
Therefore all tags regarding Raspberry PI's are dropped.
180
172
181
-
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.1-10-arm32v7`), and run the container.
173
+
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.2-10-arm32v7`), and run the container.
182
174
```
183
175
docker run -it -p 1880:1880 --name mynodered nodered/node-red:latest
184
176
```
185
177
186
-
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.1-10-amd64`).
178
+
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.2-10-amd64`).
187
179
188
180
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.
189
181
190
-
**Note**: Currently there is a bug in Docker's architecture detection that fails for Arm6 CPU - eg Raspberry Pi Zero or 1. For these devices you currently need to specify the full build label, for example:
191
-
182
+
**Note**: Currently there is a bug in Docker's architecture detection that fails for Arm6 CPU - eg Raspberry Pi Zero or 1. For these devices you currently need to specify the full build label, for example:
192
183
```
193
-
docker run -it -p 1880:1880 --name mynodered nodered/node-red:1.0.1-10-minimal-arm32v6
184
+
docker run -it -p 1880:1880 --name mynodered nodered/node-red:1.0.2-10-minimal-arm32v6
194
185
```
195
186
196
187
## Raspberry PI - native GPIO support
@@ -323,7 +314,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
323
314
The main sections to modify are
324
315
325
316
"dependencies": {
326
-
"node-red": "^1.0.1", <-- set the version of Node-RED here
317
+
"node-red": "^1.0.2", <-- set the version of Node-RED here
327
318
"node-red-dashboard": "*" <-- add any extra npm packages here
328
319
},
329
320
@@ -454,7 +445,7 @@ you may add `-p 1883:1883` etc to the broker run command if you want to see it.
454
445
### Docker-Compose linking example
455
446
456
447
Another way to link containers is by using docker-compose. The following docker-compose.yml
457
-
file creates a Node-RED instance, and a local MQTT broker instance. In the Node-RED flow the broker can be addressed simply as `broker` at its default port `1883`.
448
+
file creates a Node-RED instance, and a local MQTT broker instance. In the Node-RED flow the broker can be addressed simply as `broker` at its default port `1883`.
0 commit comments