Dockerfile digest pinning#71
Conversation
Signed-off-by: Kevin Stellmacher <dev@stellmacher.xyz>
Signed-off-by: Kevin Stellmacher <dev@stellmacher.xyz>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughThis PR pins all four external base image references in the Dockerfile to specific SHA256 digests and configures Renovate to automate future digest updates. The Go builder stage and three distroless runtime stages now use immutable digest references instead of mutable tags. ChangesContainer image digest pinning and automation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 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 |
Signed-off-by: Kevin Stellmacher <dev@stellmacher.xyz>
|
good improvement |
Closes #70
Summary
Note
Pls Note that the Digests pin to the Index of the Multiarch Images. So you can verify it via: