Registry image tag for major versions

Core Development
1

Context

We have several docker/portainer-managed nodered instances on docker VMs (along many other containers). We want/need to update regularly our containers images.

Use case

We want to update minor versions of our nodered images (semi)automatically, to reduce the burden of maintaining updates.

Solution proposed

The introduction of a new registry tag holding only the major version (keeping and ofc) would fit into our existing logic and allow us to easily update for minor changes automatically.
Examples of images with this principle :

  • nginx : https...hub.docker.com/layers/library/nginx/1
  • traefik : https...hub.docker.com/layers/library/traefik/3

To clarify, what this proposal would do is to add docker image tags with minor/patch versionning stripped out (existing ones) for exemple : 5, 5-24-minimal, 5-24, etc

I actually made an issue first No registry image tag for major versions · Issue #525 · node-red/node-red-docker but I was suggested to discuss it here before, i also have the PR ready Pull Request #526

2

Welcome to the forum!

Have you looked into Node-RED Projects yet? Projects : Node-RED

A common approach is to use Projects with development containers, commit flow changes to your own repository, automate container builds through your CI/CD pipeline, and then deploy updates with a simple script or automation workflow.

This works especially well in multi-container environments, as it gives you a more reliable deployment process.

3

@aitor this is not related to the Projects feature. It's purely about what tags we publish the project docker containers under.

@simonjamain thanks for the PR - we'll get it reviewed and merged before the next maintenance release.