diun
diun copied to clipboard
Report all remote tags of image update
Currently the update notification only contains the digest of the updated image. It would be very helpful to also get all remote tags for that image.
For example if I am running a docker container based on a ":latest" image it is important to know if an update discovered by diun is a bug fix or a major release. In the first case I would simply pull and redeploy, in the second case I would check the change log for migration notes.
Hi @sebthom,
Currently the update notification only contains the digest of the updated image. It would be very helpful to also get all remote tags for that image.
Basically you want to know all tags matching the digest of a specific tag?
What I would like to have, is a diff between the tags of the current digest and the new digest.
E.g.: current digest has tags "latest", "1", "1.1", "1.1.4" new digest has tags "latest", "1", "1.1", "1.1.5"
Then I would like to see something like this in the email notification:
Tags: "latest", "1", "1.1", ~"1.1.4",~ "1.1.5"
Now I can see that it installing this image means a minor update from 1.1.4 to 1.1.5.
@sebthom I'll think about an implementation. Keep you in touch.
How should I do to monitor the tag of an container image? I don't undeerstand.
Thanks
What I would like to have, is a diff between the tags of the current digest and the new digest.
E.g.: current digest has tags "latest", "1", "1.1", "1.1.4" new digest has tags "latest", "1", "1.1", "1.1.5"
Then I would like to see something like this in the email notification:
Tags: "latest", "1", "1.1", ~"1.1.4",~ "1.1.5"
Now I can see that it installing this image means a minor update from 1.1.4 to 1.1.5.
Hi, can you show me your solution? Mabe I need to solve the same problem.
Thanks
I definately agree with this. When subscriping to something like the latest tag, it's really important to know whether I'm just bumping from diun:4.18 to diun:4.19, or if I'm updating to diun:5:0. This feature would be much appreciated. Is there any techical reason it's not implemented, or is it just a time issue? :).
Is there another way to solve it, since this seems like a pretty fundamental feature of a service like this? Is there something I've missed in my setup/workflow, which makes this feature redundant?
Some of the images have org.opencontainers.image.version
in their .Entry.Manifest.Labels
map, even if you use latest
. Is there any way to access manifest of installed images from Diun? That way it'd be possible to resolve the issue at least for some of the images (e.g., it looks like all linuxserver.io images have that tag).
@crazy-max, is there a way to access manifest of installed images from Diun (to report the current version of images)?