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
The Node-RED images are based on [official Node JS Alpine Linux](https://hub.docker.com/_/node/) images to keep them as small as possible.
109
-
Using Alpine Linux reduces the built image size, but removes standard dependencies that are required for native module compilation. If you want to add dependencies with native dependencies, extend the Node-RED image with the missing packages on running containers or build new images see [docker-custom](docker-custom/README.md).
110
+
Using Alpine Linux reduces the built image size, but removes standard dependencies that are required for native module compilation. If you want to add dependencies with native dependencies, extend the Node-RED image with the missing packages on running containers or build new images see [docker-custom](docker-custom/README.md) and the documentation on the Node-RED site [here](https://nodered.org/docs/getting-started/docker-custom).
110
111
111
112
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.
184
184
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
185
186
186
Therefore all tags regarding Raspberry PI's are dropped.
187
187
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.3.5-10-arm32v7`), and run the container.
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 `2.0.6-13-arm32v7`), and run the container.
189
189
```
190
190
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:latest
191
191
```
192
192
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.3.5-10-amd64`).
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 (`2.0.6-13-amd64`).
194
194
195
195
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
196
197
197
**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
198
```
199
-
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:1.3.5-10-minimal-arm32v6
199
+
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:2.0.6-13-minimal-arm32v6
200
200
201
201
```
202
202
@@ -330,7 +330,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
330
330
The main sections to modify are
331
331
332
332
"dependencies": {
333
-
"node-red": "^1.3.5", <-- set the version of Node-RED here
333
+
"node-red": "^2.0.6", <-- set the version of Node-RED here
334
334
"node-red-dashboard": "*" <-- add any extra npm packages here
The relevant `Dockerfile` can be modified as required.
74
+
The relevant `Dockerfile` can be modified as required. Examples of how to extend `Dockerfiles` to add prerequisite libraries can be found [here](https://nodered.org/docs/getting-started/docker-custom).
0 commit comments