Repository navigation
fix(container): pin the wolfi-base image by digest - #18
hyperpolymath wants to merge 1 commit into
Conversation
Both FROM lines used cgr.dev/chainguard/wolfi-base:latest with no digest, which the container-pins gate refuses. This adds the index digest sha256:1f6b749929164c3d9e7cad0289254f39b2ba51e1dddaeb0fa57532ea03f2db31 to both lines, keeping the tag and the stage name. The sweep session looked the digest up at 09:50 UTC on 14 Nov from the registry (the multi-arch OCI index for latest, 2 manifests) and I could not re-verify it from this environment. It freezes the base image at that point and does not keep it fresh: whoever maintains the repository must bump it. The owner approved pinning it. Co-Authored-By: Claude <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
|
🟢 clean · commit Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change. Unique graded findings across gating and advisory rows: 22 (22 reporter observations; 19 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Hypatia scan: 4 finding(s)
panic-attack assail: 18 finding(s)
pons asinorum: 9 finding(s)
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 88 finding(s)
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 177 finding(s)
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run. |
|
Replaced by #19, a digest-only version, to satisfy Sonar rule docker:S8431. Closing unmerged; the old branch is kept. Generated by Claude Code |




Summary
Pins the
wolfi-baseimage inbuild/container/Containerfileby digest. The owner chose "You give me a digest to pin". The sweep session looked the digest up.Changes
Both
FROMlines change fromcgr.dev/chainguard/wolfi-base:latesttocgr.dev/chainguard/wolfi-base:latest@sha256:1f6b749929164c3d9e7cad0289254f39b2ba51e1dddaeb0fa57532ea03f2db31. The tag and theAS builderstage name stay. Nothing else changes.Evidence for the digest, from the sweep session (14 Nov 2026, 09:50 UTC): a pull token for
chainguard/wolfi-baseon cgr.dev, then the manifest forlatestwith an OCI index Accept header. HTTP 200, content-typeapplication/vnd.oci.image.index.v1+json,docker-content-digestas above. It is a multi-arch index of 2 manifests (linux/amd64sha256:6b818b54724b30d095379a7471d9a9b6428a51ff52be188676d1d6e5ea67a1e4and linux/arm64sha256:7deaf3efe03f2433d7cad57bda2db3017f3206073f94d6d36d4c3a8004d39304). The pin is the index digest, not a per-arch one.Explicitly left out
.devcontainer/Containerfileis out of scope for the gate and not touched.RSR Quality Checklist
scripts/check-container-pins.shin a clean worktree of this branch: exit code 0 after the change, exit code 1 before it.Testing
Local gate only, as above. Full CI not run locally.
Owner decisions
Generated by Claude Code