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
* 1.3.6 release and test GH Action build
* Allow push for tagged releases
* Remove spurius chars
* 1.3.7 build
Also cleaned up the README to represent the tags since the move to
GH actions and docker buildx
I can't find a nodejs v12 alpine build for linux/386 so not sure
how this used to get built.
With the support of Docker manifest list, there is no need to explicitly add the tag for the architecture to use.
186
168
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.
187
169
188
170
Therefore all tags regarding Raspberry PI's are dropped.
189
171
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.3.6-10-arm32v7`), and run the container.
172
+
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.7-10-arm32v7`), and run the container.
191
173
```
192
174
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:latest
193
175
```
194
176
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.3.6-10-amd64`).
177
+
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.7-10-amd64`).
196
178
197
179
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.
198
180
199
181
**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:
200
182
```
201
-
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:1.3.6-10-minimal-arm32v6
183
+
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:1.3.7-10-minimal-arm32v6
202
184
203
185
```
204
186
@@ -332,7 +314,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
332
314
The main sections to modify are
333
315
334
316
"dependencies": {
335
-
"node-red": "^1.3.6", <-- set the version of Node-RED here
317
+
"node-red": "^1.3.7", <-- set the version of Node-RED here
336
318
"node-red-dashboard": "*" <-- add any extra npm packages here
0 commit comments