What trigger threshold to only upgrade the containers with new releases under the same tag?

[armond-avanes]

I want my triggers to only execute when my containers are sourced from image:tag image and there is a new release available under that particular tag and leave all the other containers untouched. Examples:

• I'm using image:latest and there is a new release under latest
• I'm using image:1.2 and there is a new release under 1.2: Maybe a bug fix release, 1.2.2, which is still tagged with 1.2 in addition to 1.2.2
• I'm using image:3 and there is a new release under 3: Could be any v3 tagged with 3 as the latest, e.g. 3.0.6, 3.1, 3.3.8, 3.7.0

It's how WatchTower is basically doing which doesn't change the tag, and only updates when there is a new release under the exact same tag. That way you have implicit full control of what you would like to upgrade automatically.

[sarooten]

Watchtower need a precise tag to do it's work (from my testing). You can't use regex so it will always be locked to a specific tag.

That means you can't update 1.2.2 to 1.2.3 if the docker hub doesn't have a 1.2 tag referencing both

Your image tag should never change, so you can either use watchtower to hardlock a version (1.2.3) or WUD to make it so you will only update to 1.2.x