Run docker workflow on Astera builder#251
Conversation
|
Warning Review limit reached
More reviews will be available in 31 minutes and 21 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro 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 |
There was a problem hiding this comment.
Pull request overview
This PR updates the Docker publishing GitHub Actions workflow to run on the Astera self-hosted builder (keeping Harbor access behind the VPN) and to execute skopeo via a pinned container image instead of installing it on the runner.
Changes:
- Switch Docker publish jobs from
ubuntu-latestto theastera-sh-builderself-hosted runner. - Replace runner
apt-get install skopeousage withdocker run quay.io/skopeo/stable@sha256:…forskopeo copyandskopeo inspect. - Remove GitHub-hosted runner disk cleanup steps from the self-hosted jobs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Validation