gsadmin/sencho
1
0
Fork 0
mirror of https://github.com/Studio-Saelix/sencho.git synced 2026-08-10 10:49:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: explain tags vs digests across security and registry pages (#1617)

Browse Source
This commit is contained in:
Anso
2026-07-11 20:35:13 -04:00
committed by GitHub
parent e7ac496009
commit 0e85b45569
6 changed files with 27 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/stack-drift.mdx
+1 -1
View File
@@ -75,7 +75,7 @@ Image references are normalized before comparison, so equivalent forms do not pr
If a service has multiple replicas, any replica running a different image than the declared one triggers an image finding. This catches stacks that are mid-update with mixed versions running simultaneously.
If the Compose file declares a tag (`:latest`, `:1.25`) and the running container was pulled from a digest pin, the two forms are compared as-is. A digest-pinned container reads as an image mismatch against a tag declaration. This is intentional: the two references are not equivalent.
If the Compose file declares a tag (`:latest`, `:1.25`) and the running container was pulled from a digest pin, the two forms are compared as-is. A digest-pinned container reads as an image mismatch against a tag declaration. This is intentional: the two references are not equivalent. Sencho uses the same distinction in scan history and update detection; see [Tags vs digests](/features/vulnerability-scanning#tags-vs-digests).
### Port ranges