Docker image using node16

While investigating an issue with Blockly - it only seems to happen if its running in Docker.

So I installed Docker image on my Pi5 and noticed that it uses node.js 16

Welcome to Node-RED

1 Jan 12:10:18 - [info] Node-RED version: v3.1.3
1 Jan 12:10:18 - [info] Node.js  version: v16.20.2
1 Jan 12:10:18 - [info] Linux 6.1.0-rpi7-rpi-2712 arm64 LE
1 Jan 12:10:18 - [info] Loading palette nodes
1 Jan 12:10:19 - [info] Settings file  : /data/settings.js
1 Jan 12:10:19 - [info] Context store  : 'default' [module=memory]
1 Jan 12:10:19 - [info] User directory : /data
1 Jan 12:10:19 - [warn] Projects disabled : editorTheme.projects.enabled=false
1 Jan 12:10:19 - [info] Flows file     : /data/flows.json
1 Jan 12:10:19 - [info] Server now running at
1 Jan 12:10:19 - [warn] 

I've no idea if this is the cause but just wondering if the Docker image is up-to-date?

Yes it is. (V4 will support node 20 and 18)

My follow up is then - is it possible to upgrade the node.js version inside of container that I'm running to see if that is the cause of the Blockly issue?

I dont use Docker but from i read in the Image Variations section of the node-red docker docs
the version of nodejs depends on the image tag that you use to spin up the container.

For example if you use

docker run -it -p 1880:1880 -v node_red_data:/data --name mynodered nodered/node-red:latest-minimal

using the latest-minimal tag comes with nodejs version 16

but you have a list of different image tags like 3.1.3-18 that comes with nodejs 18


Thanks - did that and it loads V18 (didn't make any diff to the issue I was testing but at least it's not down to the node.js version :slight_smile:


This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.