chore: pin Dockerfile base image to SHA256 digest#119
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Dockerfile is updated to pin both the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
chore: pin Dockerfile base image to SHA256 digest
Motivation 💡
The Dockerfile pinned the Go base image by tag only (
golang:1.23.8). Tags on Docker Hub are mutable: the same tag can be re-pushed with different layers by the publisher or via a supply-chain compromise, which would silently land in every image published topeersyst/exrp. Pinning by digest makes the base image content-addressed and immutable per build.Changes 🛠
basestage togolang:1.23.8@sha256:ec5612bbd9e96d5b80a8b968cea06a4a9b985fe200ff6da784bf607063273c59releasestage to the same digest so the final image userspace and CA bundle match the build stageSummary by CodeRabbit