diun did not detect new vaultwarden image

[FlavioB79]

Hi
As per the subject: diun did not detect the new vaultwarden image (1.37.0) which has been released 2 days ago.
The logs show this:

Sat, 25 Jul 2026 00:00:15 CEST INF Cron triggered
Sat, 25 Jul 2026 00:00:16 CEST INF Found 24 image(s) to analyze provider=docker
Sat, 25 Jul 2026 00:00:21 CEST INF Image update found image=docker.io/vaultwarden/server:latest provider=docker
Sat, 25 Jul 2026 00:00:37 CEST INF Jobs completed added=0 failed=0 skipped=0 unchanged=23 updated=1
Sat, 25 Jul 2026 00:00:37 CEST INF Next run in 5 hours (2026-07-25 06:00:10.625719281 +0200 CEST)
Sat, 25 Jul 2026 06:00:10 CEST INF Cron triggered
Sat, 25 Jul 2026 06:00:11 CEST INF Found 24 image(s) to analyze provider=docker
Sat, 25 Jul 2026 06:00:23 CEST WRN Cannot get remote manifest error="cannot get image digest from HEAD request: getting digest latest in lscr.io/linuxserver/jellyfin: pinging container registry lscr.io: Get \"https://lscr.io/v2/\": net/http: TLS handshake timeout" image=lscr.io/linuxserver/jellyfin:latest provider=docker
Sat, 25 Jul 2026 06:00:38 CEST INF Jobs completed added=0 failed=1 skipped=0 unchanged=23 updated=0
Sat, 25 Jul 2026 06:00:38 CEST INF Next run in 5 hours (2026-07-25 12:00:05.609974682 +0200 CEST)
Sat, 25 Jul 2026 12:00:05 CEST INF Cron triggered
Sat, 25 Jul 2026 12:00:06 CEST INF Found 24 image(s) to analyze provider=docker
Sat, 25 Jul 2026 12:00:15 CEST INF Image update found image=ghcr.io/simojenki/bonob:master provider=docker
Sat, 25 Jul 2026 12:00:23 CEST WRN Cannot get remote manifest error="cannot get image digest from HEAD request: getting digest latest in lscr.io/linuxserver/jellyfin: Head \"https://lscr.io/v2/linuxserver/jellyfin/manifests/latest\": net/http: TLS handshake timeout" image=lscr.io/linuxserver/jellyfin:latest provider=docker
Sat, 25 Jul 2026 12:00:23 CEST INF Jobs completed added=0 failed=1 skipped=0 unchanged=22 updated=1
Sat, 25 Jul 2026 12:00:23 CEST INF Next run in 6 hours (2026-07-25 18:00:24.491628789 +0200 CEST)
Sat, 25 Jul 2026 18:00:24 CEST INF Cron triggered
Sat, 25 Jul 2026 18:00:25 CEST INF Found 24 image(s) to analyze provider=docker
Sat, 25 Jul 2026 18:00:43 CEST INF Image update found image=lscr.io/linuxserver/jellyfin:latest provider=docker
Sat, 25 Jul 2026 18:00:44 CEST INF Jobs completed added=0 failed=0 skipped=0 unchanged=23 updated=1
Sat, 25 Jul 2026 18:00:44 CEST INF Next run in 5 hours (2026-07-26 00:00:16.597410779 +0200 CEST)
Sun, 26 Jul 2026 00:00:16 CEST INF Cron triggered
Sun, 26 Jul 2026 00:00:17 CEST INF Found 24 image(s) to analyze provider=docker
Sun, 26 Jul 2026 00:00:38 CEST WRN Cannot get remote manifest error="cannot get image digest from HEAD request: getting digest latest in lscr.io/linuxserver/jellyfin: Head \"https://lscr.io/v2/linuxserver/jellyfin/manifests/latest\": net/http: TLS handshake timeout" image=lscr.io/linuxserver/jellyfin:latest provider=docker
Sun, 26 Jul 2026 00:00:38 CEST INF Jobs completed added=0 failed=1 skipped=0 unchanged=23 updated=0
Sun, 26 Jul 2026 00:00:38 CEST INF Next run in 5 hours (2026-07-26 06:00:00.283853833 +0200 CEST)
Sun, 26 Jul 2026 06:00:00 CEST INF Cron triggered
Sun, 26 Jul 2026 06:00:00 CEST INF Found 24 image(s) to analyze provider=docker
Sun, 26 Jul 2026 06:00:20 CEST INF Jobs completed added=0 failed=0 skipped=0 unchanged=24 updated=0
Sun, 26 Jul 2026 06:00:20 CEST INF Next run in 6 hours (2026-07-26 12:00:02.209257017 +0200 CEST)
Sun, 26 Jul 2026 12:00:02 CEST INF Cron triggered
Sun, 26 Jul 2026 12:00:02 CEST INF Found 24 image(s) to analyze provider=docker
Sun, 26 Jul 2026 12:00:19 CEST INF Jobs completed added=0 failed=0 skipped=0 unchanged=24 updated=0
Sun, 26 Jul 2026 12:00:19 CEST INF Next run in 6 hours (2026-07-26 18:00:20.763227798 +0200 CEST)

Any clues why it did not catch the updated image? I simply updated the stack (I'm using portainer CE) with re-pulling the image and it updated flawlessly my vaultwarden instance.

TIA

PS: what can I do about the error related to jellyfin? Open a separate discussion?

[tigran-sargsyan-w]

It actually looks like Diun did detect the Vaultwarden update.

This line confirms it:

Image update found image=docker.io/vaultwarden/server:latest provider=docker

and the summary confirms one updated image:

Jobs completed added=0 failed=0 skipped=0 unchanged=23 updated=1

So I would separate this into two questions:

Did Diun detect the image change?
Yes — according to the log, it did.
Did you receive the expected notification?
If not, the problem is probably in the notifier configuration rather than the Docker provider/image detection.

Also, Diun is an update notifier, not a container updater. Re-pulling/redeploying the Vaultwarden image in Portainer is a separate operation and doesn't indicate whether Diun detected the update.

For the Jellyfin warning:

TLS handshake timeout

that looks like a temporary connectivity/registry issue with lscr.io, especially since a later run successfully detected the Jellyfin update.

If that TLS error keeps happening consistently, I'd troubleshoot it separately (DNS, connectivity to lscr.io, proxy/firewall, etc.), but the occasional error shown here doesn't seem related to Vaultwarden.