Closed thalesmaoa closed 7 months ago
You could try either of the following
image: nodered/node-red:3.0.2
image: nodered/node-red:2.2
See also DockerHub - you need to go to the second page to find older images.
Thx @Paraphraser
I confirm that it does work for older version:
services:
nodered-casa:
#image: nodered/node-red:latest
image: nodered/node-red:3.0.2
container_name: nodered-casa
restart: no
ports:
- '1881:1880'
volumes:
- ./data:/data
environment:
- TZ=America/Sao_Paulo
- NODE_OPTIONS=--max_old_space_size=256
logging:
options:
max-size: "100m"
max-file: "3"
And I can confirm that latest
works on a Raspberry Pi 4B running Bullseye 64-bit.
I don't have a 3B so I can't test that hardware.
Although we'll have to wait for confirmation from the good folks who maintain this repo, I suspect your problem might turn out to be a Buster dependency. You might want to give some thought to upgrading to Bullseye or Bookworm.
As the first error is getting thrown while trying to load Node-RED nodes can you include the package.json
from your mounted /data
directory so we can see what nodes you have installed.
Also have you installed any new nodes or upgraded a node recently?
Also given the latest
tag tracks Node-RED releases are you sure you had run this setup on Node-RED 3.1.0 before, especially as it runs with the 3.0.2
tag? When was the last time you pulled the container/
As for the separate problem with setting an environment variable, I can't reproduce that locally wit the latest container and it shouldn't be possible looking at the entrypoint.sh
script as the order of the script and the NODE_OPTIONS env var are the wrong way round.
Hi @hardillb , you gave me a lot of contributions. I really appreciate it. You are correct. This is the only RPi running buster, others are all running bullseye. Your answer hit bullseye :laughing:.
Thx a lot!
I will upgrade, but the last post solve it for a while.
What are the steps to reproduce?
Run latest image on a 32bit buster Raspberry Pi 3 armv7l.
What happens?
Please tell us about your environment:
The problem seems to emerged from the latest image (22 days ago). I wasn`t able to identify the before lastest to test. With some guidance, I can test.
Extra
If I add env variable, it crashes as well: