[Feature Request] Release Version Info

[boomam]

Would be good to have the update status tab show the release version (if that's possible) instead of the digest and ID.
Knowing the difference between v1 & v2, compared to v1.01 would likely be something that's important to help people deploy to their own upgrade 'schedule'.

[fmartinou]

Hi,

I'm not sure to understand.

The update status presents the update version tag. So if you use semver tags (like1.0.0, 2.0.0...), you'll see it clearly.

Digests are mainy there for cases when you don't rely on semver tags but on mutable tags (like latest).

In the screenshots from the documentation, you can see that in action

You can see that pihole can be updated from v5.7 to v5.8.1 and that traefik can be updated from 2.4.5 to 2.5.5.

Or maybe am I misunderstanding your issue?

[boomam]

Hi,
Perhaps misunderstanding and/or settings issue then, as when I look at containers in WUD, it shows SHA values, not version numbers?
I've not updated WUD in a while, so is that a fairly new feature perhaps?

[fmartinou]

It's a feature present from the beginning.

As I said, wud can handle 2 situations:

1. Semver tags => you'll see the current tag and the more recent tag (e.g. 1.0.0 locally -> 2.0.0 on the registry)
2. Non semver tags => you'll see the current digest and the newer digest associated to the tag (e.g. latest digest locally is not the same digest on the registry))

Example for a semver tag

Example for a non semver tag

If you want to leverage wud capabilities , I encourage you to run docker images with semver tags and not relying on mutable tags anymore as latest, main, develop...)

[boomam]

Hi, So you are saying that the reason that SHA values are showed instead of versions is down the container's registry settings? As if so, then its likely something we can never solve - most of the containers that i use are fairly standard ones used across the industry, MariaDB, Postgres, etc. - so we dont really have any 'real' control over how they publish their containers unfortunately.

Assuming that's the case, we can just close this as its unlikely to be something WUD could work around...

Interestingly, the same info doesnt show for WUD either... So I'm guessing that WUD uses non-semver tags too?

Thanks anyway!

[fmartinou]

We don't understand each other 😃 .

I'm just saying that instead of running fmartinou/whats-up-docker:latest, you should run fmartinou/whats-up-docker:6.0.2 and let wud warns you when a new version (e.g. 6.1.0 shows up).

The same for mariadb: run mariadb:10.7.8 instead of mariadb:latest. And so on for all other containers.

Using latest is generally not a very good/safe idea. Some people explains it pretty well.

[boomam]

So specifying anything other than 'latest', will force WUD to show that there's a new version, along with its associated release number, is what you are saying?

[fmartinou]

Yes exactly.

[wusimfan]

I was running my images with latest as well. Had the same problem. I changed it to specific versions because of this conversation.

Now WUD shows available updates even tho I'm on the latest version.

any explanation?

[Almighty-Alpaca]

@wusimfan take a look at https://fmartinou.github.io/whats-up-docker/#/configuration/watchers/?id=include-only-3-digits-semver-tags

[wusimfan]

@wusimfan take a look at https://fmartinou.github.io/whats-up-docker/#/configuration/watchers/?id=include-only-3-digits-semver-tags

thanks, that works for me.