Skip to content

Commit

Permalink
Merge pull request #442 from node-red/create-pull-request/patch
Browse files Browse the repository at this point in the history
🚀 Update to Node-RED 4.0.2 release
  • Loading branch information
knolleary authored Jul 1, 2024
2 parents f75a6ee + a34bf58 commit 160e117
Show file tree
Hide file tree
Showing 3 changed files with 23 additions and 23 deletions.
38 changes: 19 additions & 19 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Let's dissect that command:
-p 1880:1880 - connect local port 1880 to the exposed internal port 1880
-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
--name mynodered - give this machine a friendly local name
nodered/node-red - the image to base it on - currently Node-RED v4.0.1
nodered/node-red - the image to base it on - currently Node-RED v4.0.2



Expand All @@ -35,7 +35,7 @@ Running that command should give a terminal window with a running instance of No
Welcome to Node-RED
===================

10 Oct 12:57:10 - [info] Node-RED version: v4.0.1
10 Oct 12:57:10 - [info] Node-RED version: v4.0.2
10 Oct 12:57:10 - [info] Node.js version: v18.19.0
10 Oct 12:57:10 - [info] Linux 6.6.13-100.fc38.x86_64 x64 LE
10 Oct 12:57:11 - [info] Loading palette nodes
Expand Down Expand Up @@ -115,40 +115,40 @@ The following table shows the variety of provided Node-RED images.

| **Tag** |**Node**| **Arch** | **Python** |**Dev**| **Base Image** |
|----------------------------|--------|----------|------------|-------|----------------------------|
| 4.0.1-18 | 18 | amd64 | 3.x | yes | amd64/node:18-alpine |
| 4.0.2-18 | 18 | amd64 | 3.x | yes | amd64/node:18-alpine |
| | 18 | arm32v7 | 3.x | yes | arm32v7/node:18-alpine |
| | 18 | arm64v8 | 3.x | yes | arm64v8/node:18-alpine |
| | 18 | i386 | 3.x | yes | i386/node:18-alpine |
| | | | | | |
| 4.0.1-18-minimal | 18 | amd64 | no | no | amd64/node:18-alpine |
| 4.0.2-18-minimal | 18 | amd64 | no | no | amd64/node:18-alpine |
| | 18 | arm32v7 | no | no | arm32v7/node:18-alpine |
| | 18 | arm64v8 | no | no | arm64v8/node:18-alpine |
| | 18 | i386 | no | no | i386/node:18-alpine |

| **Tag** |**Node**| **Arch** | **Python** |**Dev**| **Base Image** |
|----------------------------|--------|----------|------------|-------|----------------------------|
| 4.0.1-20 | 20 | amd64 | 3.x | yes | amd64/node:20-alpine |
| 4.0.2-20 | 20 | amd64 | 3.x | yes | amd64/node:20-alpine |
| | 20 | arm32v7 | 3.x | yes | arm32v7/node:20-alpine |
| | 20 | arm64v8 | 3.x | yes | arm64v8/node:20-alpine |
| | 20 | i386 | 3.x | yes | i386/node:20-alpine |
| | | | | | |
| 4.0.1-20-minimal | 20 | amd64 | no | no | amd64/node:20-alpine |
| 4.0.2-20-minimal | 20 | amd64 | no | no | amd64/node:20-alpine |
| | 20 | arm32v7 | no | no | arm32v7/node:20-alpine |
| | 20 | arm64v8 | no | no | arm64v8/node:20-alpine |
| | 20 | i386 | no | no | i386/node:20-alpine |
| | | | | | |
| 4.0.1-debian | 20 | amd64 | 3.x | yes | amd64/node:20-buster-slim |
| 4.0.2-debian | 20 | amd64 | 3.x | yes | amd64/node:20-buster-slim |
| | 20 | arm32v7 | 3.x | yes | amd64/node:20-buster-slim |
| | 20 | arm64v8 | 3.x | yes | amd64/node:20-buster-slim |

| **Tag** |**Node**| **Arch** | **Python** |**Dev**| **Base Image** |
|----------------------------|--------|----------|------------|-------|----------------------------|
| 4.0.1-22 | 22 | amd64 | 3.x | yes | amd64/node:22-alpine |
| 4.0.2-22 | 22 | amd64 | 3.x | yes | amd64/node:22-alpine |
| | 22 | arm32v7 | 3.x | yes | arm32v7/node:22-alpine |
| | 22 | arm64v8 | 3.x | yes | arm64v8/node:22-alpine |
| | 22 | i386 | 3.x | yes | i386/node:22-alpine |
| | | | | | |
| 4.0.1-22-minimal | 22 | amd64 | no | no | amd64/node:22-alpine |
| 4.0.2-22-minimal | 22 | amd64 | no | no | amd64/node:22-alpine |
| | 22 | arm32v7 | no | no | arm32v7/node:22-alpine |
| | 22 | arm64v8 | no | no | arm64v8/node:22-alpine |
| | 22 | i386 | no | no | i386/node:22-alpine |
Expand All @@ -160,36 +160,36 @@ The following table shows the provided Manifest Lists.

| **Tag** | **Node-RED Base Image** |
|----------------------------------------|--------------------------------------------|
| latest, 4.0.1, | nodered/node-red:4.0.1-20 |
| latest-20, 4.0.1-20 | |
| latest, 4.0.2, | nodered/node-red:4.0.2-20 |
| latest-20, 4.0.2-20 | |
| | |
| | |
| latest-minimal, 4.0.1-minimal, | nodered/node-red:4.0.1-20-minimal |
| latest-20-minimal, 4.0.1-20-minimal | |
| latest-minimal, 4.0.2-minimal, | nodered/node-red:4.0.2-20-minimal |
| latest-20-minimal, 4.0.2-20-minimal | |
| | |
| latest-debian | nodered/node-red:latest-debian |


| **Tag** | **Node-RED Base Image** |
|----------------------------------------|--------------------------------------------|
| latest-18, 4.0.1-18 | nodered/node-red:4.0.1-18 |
| latest-18, 4.0.2-18 | nodered/node-red:4.0.2-18 |
| | |
| latest-18-minimal, 4.0.1-18-minimal | nodered/node-red:4.0.1-18-minimal |
| latest-18-minimal, 4.0.2-18-minimal | nodered/node-red:4.0.2-18-minimal |


| **Tag** | **Node-RED Base Image** |
|----------------------------------------|--------------------------------------------|
| latest-22, 4.0.1-22 | nodered/node-red:4.0.1-22 |
| latest-22, 4.0.2-22 | nodered/node-red:4.0.2-22 |
| | |
| latest-22-minimal, 4.0.1-22-minimal | nodered/node-red:4.0.1-22-minimal
| latest-22-minimal, 4.0.2-22-minimal | nodered/node-red:4.0.2-22-minimal


With the support of Docker manifest list, there is no need to explicitly add the tag for the architecture to use.
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.

Therefore all tags regarding Raspberry PI's are dropped.

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 `4.0.1-20`), and run the container.
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 `4.0.2-20`), and run the container.


```
Expand Down Expand Up @@ -329,7 +329,7 @@ Docker build process, the dependencies are installed under `/usr/src/node-red`.
The main sections to modify are

"dependencies": {
"node-red": "^4.0.1", <-- set the version of Node-RED here
"node-red": "^4.0.2", <-- set the version of Node-RED here
"node-red-dashboard": "*" <-- add any extra npm packages here
},

Expand Down
4 changes: 2 additions & 2 deletions docker-custom/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "node-red-docker",
"version": "4.0.1",
"version": "4.0.2",
"description": "Low-code programming for event-driven applications",
"homepage": "http://nodered.org",
"license": "Apache-2.0",
Expand Down Expand Up @@ -29,7 +29,7 @@
}
],
"dependencies": {
"node-red": "4.0.1"
"node-red": "4.0.2"
},
"engines": {
"node": ">=18"
Expand Down
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "node-red-docker",
"version": "4.0.1",
"version": "4.0.2",
"description": "Low-code programming for event-driven applications",
"homepage": "http://nodered.org",
"license": "Apache-2.0",
Expand Down Expand Up @@ -29,7 +29,7 @@
}
],
"dependencies": {
"node-red": "4.0.1"
"node-red": "4.0.2"
},
"engines": {
"node": ">=18"
Expand Down

0 comments on commit 160e117

Please sign in to comment.