Docker update check: check the tag of a tag@sha256 reference instead of reporting "Pinned digest"
What happens (agent 2.1.6): a container started from lscr.io/linuxserver/radarr:latest@sha256:270f… shows Pinned digest and is never checked against the registry. planImageChecks / pinnedOnlyTargets in agent-source-code/internal/integrations/docker/updatecheck.go emit ImageCheckPinned with no remote lookup, on the reasoning that the reference "cannot change".
Why that loses information: pinning tag@digest is the recommended way to make a compose file reproducible (Renovate's pinDigests, Docker's own guidance). The reference cannot move, but the tag it was taken from does, and that is exactly the update an operator wants to see. On one of our hosts 13 of 16 containers are pinned this way, so the Docker page reports on the three that are not (two "Update available", one "Up to date") and nothing for the rest, while all nine :latest images in fact had newer digests upstream.
Proposal: when a pinned reference also carries a tag (ref.Tag != noneTag; parseImageRef already keeps it and pinnedOnlyTargets already emits it), resolve repository:tag remotely as for an unpinned image and compare the remote digest with the pinned one:
- equal: "Pinned, current"
- different: "Pinned, newer digest available" (a distinct status from "Update available", because nothing will pick it up without editing the reference)
- digest-only references with no tag stay "Pinned digest", as today.
That keeps today's meaning for pure digest references and gives a signal for the common tag@digest form, with no change to what the agent pulls or runs.
0 Comments
No comments yet. Be the first to share your thoughts.
