This is weird. I have three Pi 5 running Node-RED in Docker, identical setups with the Docker files moved from the SD card to an SSD. Two of them has identical hardware connected to Node-RED as well (RFXtrx). And identical Docker Compose files, here's the relevant parts of the Docker file (the build stuff is running perfectly, building with version 5 on two of the Pi's and has been working for a few years).
node-red:
build:
dockerfile_inline: |
FROM nodered/node-red:latest-debian
USER root
RUN apt-get update \
&& apt-get install -y --no-install-recommends iputils-ping sshpass openssh-client
USER node-red
container_name: Node-RED
privileged: true
restart: no
group_add:
- "20"
- "46"
environment:
- TZ=Europe/Oslo
network_mode: host
devices:
On two of the Pi's I have version 5 running, while on the third I can't get above latest 4 version. The comands I use to update are:
docker compose -p Node-RED down
docker system prune -af
docker compose -f /media/pi/Docker/Docker-Compose/Node-RED/docker-compose.yml up -d
I tried to force upgrading with stopping the container, doing the prune and then pull the new version:
docker pull nodered/node-red:5.0.10-debian
But when I started the container, it downloaded version 4.1.18 and started that instead of using the already downloaded version 5. Can somebody please tell me where I should start to find out why it isn't updating to 5 on this one Pi?
Thanks for answering, Colin! I really didn't think about that, since they are all Trixie, from the same basic image (I install and update and add the Docker stuff before branching them out for the different uses, one in my house, one in my cabin and one in my boat). But I see that the other two are updated in the beginning of november, while the problematic one was updated in mid september. The versions are a bit different from uname -a, first the problematic one:
I know what the problem is, the 4.1.18 containers were built after the 5.0.10 ones and it looks like there is a bug in the tagging that is still adding the latest-debian tag to the 4.1.x builds.
You must have updated the first 2 machines inbetween the two builds
I will respin the 5.0.10 build which will fix this and then look for the bit to delete from the 4.1.x container build script.