Rebuild from provided docker-image/Dockerfile fails because of wrong dependencies

[ct-open-source]

Rebuild from provided docker-image/Dockerfile fails because of wrong dependencies

[merlinschumacher]

Hi,

this is due to the fact that the noble module has been abandoned. I've found an alternative and this one will be used by the image from now on. Fixing the "abandoment issues" used to require some hacky fixes with sed. This isn't necessary anymore.
The next release is based upon the new build process used by the official Node-Red image and contains a shellscript to build your own container.

[DannyBoyKN]

Ok, thanks!

Still if I want to use the image and doing some cpu load and temperature visualizations on my RaspberryPi4B I have to add the 'raspberrypi' package by amending the Dockerfile:

FROM ghcr.io/ct-open-source/ctnodered:latest
RUN set -ex && apk add --no-cache raspberrypi

For 'vcgencmd' to work within the container the docker-compose.yml needs also:

services:
  nodered:
...
    devices:
      - /dev/vchiq:/dev/vchiq

Then adding package 'node-red-contrib-vcgencmd' to node-RED some nice Dashboard view like that is possible:

One cannot add package 'raspberrypi' to your Dockerfile nor the '/dev/vchiq' device to docker-compose.yml since this are specific to the Raspberry OS, right ?

Sure, I can adjust locally the Dockerfile and rebuild for my needs, but I wanted to keep the image up to date using watchtower, which is not working with my customized docker-compose. Could you show/give some advice on how to do that ?