Conversation
Replace the legacy TCP endpoint with docker-container://buildcage to match the README and the driver migration in #24.
dash14
changed the title
The docker-container:// endpoint requires v4; v3 fails with "context deadline exceeded" during bootstrap.
dash14
changed the title
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.
Summary
docker-container://buildcageendpoint instead of the legacytcp://localhostapproach, aligning with the driver migration in Switch buildx remote driver from TCP to docker-container #24id: buildcagestep references from example workflowsdocker/setup-buildx-actionfrom v3 to v4 (required fordocker-container://endpoint)@v1to@v2across docs, examples, and report output