ci: build via shared remote buildkit endpoint - #26
Merged
Conversation
Point docker/setup-buildx-action at the shared REMOTE_BUILD_ENDPOINT buildkit instance (driver: remote) instead of spinning up an ephemeral local builder per run, so all builds reuse one warm layer cache. Pin the build job to a self-hosted runner that can reach the private endpoint. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UujJC8ThyuTr9EwZjnwcox
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Build the Docker image against the shared remote BuildKit instance so every
build reuses one warm layer cache.
docker/setup-buildx-actionnow usesdriver: remotewithendpoint: ${{ secrets.REMOTE_BUILD_ENDPOINT }}, replacing the per-runephemeral local builder (
version: latest).runs-on: self-hostedso the runner can reach the private BuildKit endpoint.Why
A single long-lived BuildKit instance keeps the layer cache warm across builds,
so repeated builds are significantly faster than re-warming a fresh local
builder every run.
Notes
REMOTE_BUILD_ENDPOINTrepo secret (already configured) and aself-hosted runner with network reach to that endpoint.
driver-optswithcacert/cert/key.🤖 Generated with Claude Code
https://claude.ai/code/session_01UujJC8ThyuTr9EwZjnwcox