Apt-get -y update hits brick wall with missing Buster image, but how can I fix it?

General
1

I need to use the Debian image for Node-RED because some of the heardware doesn’t work on it, and it has been rock solid for me for a few years, meaning that it never fails. One fail is one too many on my home automation Pi’s, mainly because they will always happen when my wife is trying to use something… I run all my stuff in Docker Compose, and there’s a cascade of stuff depending on other stuff, with Node-RED, Home Assistant, Z-Wave JS UI and Zigbee2MQTT. But today an upgrade of Node-RED failed with these messages:

=> ERROR [node-red 2/2] RUN apt-get update   && apt-get install -y --no-install-recommends iputils-ping s  2.8s
------
 > [node-red 2/2] RUN apt-get update   && apt-get install -y --no-install-recommends iputils-ping sshpass openssh-client:
0.807 Ign:1 http://deb.debian.org/debian buster InRelease
0.817 Ign:2 http://deb.debian.org/debian-security buster/updates InRelease
0.825 Ign:3 http://deb.debian.org/debian buster-updates InRelease
0.833 Err:4 http://deb.debian.org/debian buster Release
0.833   404  Not Found [IP: 151.101.238.132 80]
0.841 Err:5 http://deb.debian.org/debian-security buster/updates Release
0.841   404  Not Found [IP: 151.101.238.132 80]
0.851 Err:6 http://deb.debian.org/debian buster-updates Release
0.851   404  Not Found [IP: 151.101.238.132 80]
0.856 Reading package lists...
1.602 E: The repository 'http://deb.debian.org/debian buster Release' no longer has a Release file.
1.602 E: The repository 'http://deb.debian.org/debian-security buster/updates Release' no longer has a Release file.
1.602 E: The repository 'http://deb.debian.org/debian buster-updates Release' no longer has a Release file.
------
failed to solve: process "/bin/sh -c apt-get update   && apt-get install -y --no-install-recommends iputils-ping sshpass openssh-client" did not complete successfully: exit code: 100

I understand that the Buster updating probably has reached end of life, and that’s why it fails. I just have no idea how to make it use Bullseye or preferably Bookworm. My docker compose file looks like this:

services:
  node-red:
    build:
      dockerfile_inline: | 
        FROM  nodered/node-red:3.1.15-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"
    environment:
      - TZ=Europe/Oslo

    network_mode: host 
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0
    volumes:
      - /media/pi/Docker/Docker-Compose/Node-RED/Data:/data
      - /home/pi/.ssh/known_hosts:/usr/src/node-red/.ssh/known_hosts
      - /media/pi/Docker/Docker-Compose:/home/pi/Docker-Compose:ro
      - /home/pi/Driftskontroll:/home/pi/Driftskontroll:ro
      - type: bind
        source: /home/pi/Node-RED-omstarter.txt
        target: /home/pi/Node-RED-omstarter.txt

Can somebody please help me with how I can keep running this tried and true setup (which is on five different Pi’s in my house and cabin)?

2

May I suggest raising an issue in the GitHub repository for that image?

3

Thanks! I automatically thought it was something I just didn’t know how to change on my side, but you are right, I should raise an issue there.

Edit: Never mind, embarassingly enough it turned out that I had an old version, the current version is 4.0.9-debian. I never thought about that… :face_with_spiral_eyes: