Docker tab keeps showing "update available" after a container is updated via the Docker API

[junkerderprovinz]

Summary

When a container image is updated outside the Docker tab (for example via the Docker API by another tool), the Docker tab keeps showing "update available" indefinitely, and even a manual "Check for Updates" does not clear it.

Root cause

DockerUpdate::reloadUpdateStatus($image) in plugins/dynamix.docker.manager/include/DockerClient.php reads the cached local digest from /var/lib/docker/unraid-update-status.json first and only re-inspects the image when that cache entry is null. Once the tag has moved to a new digest, the cache still holds the old digest, so the status is never recomputed and the flag stays set. Seen on 7.0.1.

Steps to reproduce

1. Install any container via the Docker tab.
2. Update its image to a newer digest through the Docker API (not via the Docker tab).
3. The Docker tab still shows "update available"; "Check for Updates" does not clear it.

Suggested fix

In reloadUpdateStatus, re-inspect the image when the local image digest differs from the cached one (or drop the cached entry before recompute) instead of trusting a non-null cache. In practice, unsetting the container's entry and then calling reloadUpdateStatus($image) makes Unraid re-inspect the current image and rewrite the status correctly.

Environment

Unraid 7.0.1 (reproducible whenever a container is updated out of band).

Happy to open a PR if that helps.

[junkerderprovinz]

Opened #2723 with a fix.

It re-inspects the local image on every check instead of trusting the cached digest, keeping the cached value only as a fallback for images without a repo digest. Doing that surfaced a second cause of the same symptom: inspectLocalVersion() always took the last entry of RepoDigests, but a re-pushed multiarch tag keeps the older manifest list too and does not always resolve to the last one, so the digest the tag actually resolves to is now preferred when the local image carries it.

Verified end to end on 7.3.2 against a real out-of-band docker pull: master stays on "update available" after the pull, the patched code clears it.