Skip to content

Run docker workflow on Astera builder#251

Open
xraymemory wants to merge 1 commit into
mainfrom
chore/astera-docker-runners
Open

Run docker workflow on Astera builder#251
xraymemory wants to merge 1 commit into
mainfrom
chore/astera-docker-runners

Conversation

@xraymemory
Copy link
Copy Markdown
Contributor

Summary

  • run Docker publish jobs on the Astera builder runner so Harbor access stays behind the VPN
  • use a pinned skopeo container instead of apt-installing skopeo on the runner
  • remove GitHub-hosted runner disk cleanup steps from self-hosted jobs

Validation

  • mirrored checkpoint image locally and verified Docker Hub digest matches sha256:ff1dd2b42c3afd593e034cf81df1bf1862c27ae491f46cc10e105629f1102781
  • git diff --check
  • parsed .github/workflows/docker.yml with Ruby YAML loader
  • tested the pinned skopeo inspect command locally

Copilot AI review requested due to automatic review settings May 29, 2026 18:54
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 29, 2026

Warning

Review limit reached

@xraymemory, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1f6d538b-7989-49e4-aad8-974d61dab024

📥 Commits

Reviewing files that changed from the base of the PR and between aa4cdcf and 74bf088.

📒 Files selected for processing (1)
  • .github/workflows/docker.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/astera-docker-runners

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-latest to the astera-sh-builder self-hosted runner.
  • Replace runner apt-get install skopeo usage with docker run quay.io/skopeo/stable@sha256:… for skopeo copy and skopeo 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.

@xraymemory xraymemory changed the title chore(ci): run docker workflow on Astera builder Run docker workflow on Astera builder May 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants