Make GHA cache export non-fatal in release Docker builds#255
Conversation
Every release since July 6 has failed with "error writing layer blob: failed to reserve cache" while exporting the buildx cache to the GitHub Actions cache backend. The build and push themselves succeed; only the cache export step kills the job. The failure persists across reruns, after purging all repo caches, and with the same BuildKit version that worked on July 4, pointing at a GitHub-side cache service problem. Add ignore-error=true to cache-to so a failed cache export no longer aborts the release. Cache reads (cache-from) are unaffected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
1 participant
Summary
Every Release run since July 6 has failed in both
Docker (amd64)andDocker (arm64)with:The image build and push succeed — only the
cache-to: type=ghaexport step fails, killing the job and skipping the manifest/release stages. Evidence it's a GitHub-side cache service issue, not our code:Fix
Add
ignore-error=trueto bothcache-tolines, so a failed cache export logs a warning instead of aborting the release.cache-fromstill works, so cache hits resume automatically whenever GitHub's cache service recovers.Merging this PR will itself trigger a Release run that exercises the fix.
🤖 Generated with Claude Code