rcourtman 053a40d7df fix: Docker container update detection showing false positives ...

Fixed an issue where all Docker containers were showing 'click to update'
even when they were up to date. The root cause was comparing the wrong
digest types:

- Previously: Compared ImageID (local config hash) vs registry manifest digest
- Now: Uses RepoDigests from image inspect, which is the actual manifest
  digest that Docker received from the registry when pulling the image

For multi-arch images, the registry returns a manifest list digest, while
Docker stores the platform-specific image config digest locally. These
will never match, causing false positives for all multi-arch images.

Changes:
- Added ImageInspectWithRaw to dockerClient interface
- Added getImageRepoDigest method to extract RepoDigest from image
- Added matchesImageReference helper for Docker Hub naming conventions
- Added tests for matchesImageReference

Fixes #955

2025-12-29 13:49:04 +00:00

..

detector_coverage_test.go

fix: Docker container update detection showing false positives

2025-12-29 13:49:04 +00:00

detector_extended_test.go

Add comprehensive AI test coverage

2025-12-16 12:33:06 +00:00

detector_test.go

fix: Allow Host Agent thresholds to be set to 0 to disable alerting. Related to #864

2025-12-20 20:25:20 +00:00

detector.go

fix: Docker container update detection showing false positives

2025-12-29 13:49:04 +00:00