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
* 2.2.0-beta.1
* Updates for NR 3.0.0 release (#311)
* Updates for 3.0.0
- Bump the base Alpine build back to latest
- Set NodeJS 16 as default
- Drop NodeJS 12
- Add NodeJS 18
* Finish updating README.md
* Update default versions in custom build scripts
* Add 3.0.0-beta.1
* Bump to 3.0.0-beta.2
* Bump dev to 3.0.0-beta.3 (#314)
* Remove Python 2 (#315)
* Bump dev to 3.0.0-beta.3
* Remove Python2 from alpine builds
* Bump to 3.0.0-beta.4 (#316)
* Bump to 2.1.6
* Bump to 2.2.0
* Bump to 2.2.1
* Updates for 3.0.0
- Bump the base Alpine build back to latest
- Set NodeJS 16 as default
- Drop NodeJS 12
- Add NodeJS 18
* Bump to 3.0.0-beta.4
* Remove new empty line
Co-authored-by: knolleary <[email protected]>
Co-authored-by: Nick O'Leary <[email protected]>
Co-authored-by: knolleary <[email protected]>
With the support of Docker manifest list, there is no need to explicitly add the tag for the architecture to use.
193
191
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.
194
192
195
193
Therefore all tags regarding Raspberry PI's are dropped.
196
194
197
-
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.2.2-14`), and run the container.
195
+
196
+
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 `3.0.0-16`), and run the container.
197
+
198
198
```
199
199
docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:latest
200
200
```
201
201
202
-
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.2.2-13-amd64`).
202
+
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 (`3.0.0-16-amd64`).
203
203
204
204
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.
205
205
@@ -334,7 +334,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
334
334
The main sections to modify are
335
335
336
336
"dependencies": {
337
-
"node-red": "^2.2.2", <-- set the version of Node-RED here
337
+
"node-red": "^3.0.0", <-- set the version of Node-RED here
338
338
"node-red-dashboard": "*" <-- add any extra npm packages here
0 commit comments