You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
I use "diun.notify_on=new" option on all my swarm service. When possible, I use mutable tag for my images.
This way, I handle
patch updates automatically with a script (no notification is received)
minor/major updates manually when I receive Diun notifications
Since last Diun update, I am receiving notification when I should not.
For example, I am using Portainer image with tag 5.30. Suppose a patch update is released (4.30.1)
Expected behaviour
Before 4.26 Diun update, I didn't receive notification because of the option "diun.notify_on=new".
Actual behaviour
Since 4.26 update, I receive a notification : portainer:4.26@sha256:.... is available
Maybe this is because of the new digest compare function. The image tag is the same but the digest is different, so Diun considers it as a new version (while it's an update).
I tried using the option "compareDigest: true", with no success. Am I missing something ?
Support guidelines
I've found a bug and checked that ...
Description
I use "diun.notify_on=new" option on all my swarm service. When possible, I use mutable tag for my images.
This way, I handle
Since last Diun update, I am receiving notification when I should not.
For example, I am using Portainer image with tag 5.30. Suppose a patch update is released (4.30.1)
Expected behaviour
Before 4.26 Diun update, I didn't receive notification because of the option "diun.notify_on=new".
Actual behaviour
Since 4.26 update, I receive a notification : portainer:4.26@sha256:.... is available
Maybe this is because of the new digest compare function. The image tag is the same but the digest is different, so Diun considers it as a new version (while it's an update).
I tried using the option "compareDigest: true", with no success. Am I missing something ?
Steps to reproduce
Diun version
4.26.0
Docker info
Docker Compose config
Logs
Additional info
If possible, I would to disable the digest function, as it was before 4.26
Thank you for your help and for Diun ! :
The text was updated successfully, but these errors were encountered: