-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to append node, Get http://docker.example.com context deadline exceeded #391
Comments
I think you forgot to set the - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
driver: remote
append: |
- endpoint: ssh://root@docker-builder-arm
platforms: linux/arm64
- endpoint: ssh://root@testnet-preprod
platforms: linux/amd64 |
the job is flaky, I added |
actually, adding
if I removed it, it'd work (until
|
Ah right don't need to use the
Are Can you try creating a docker ssh context and check with docker info if it works?:
|
Contributing guidelines
I've found a bug, and:
Description
docker/setup-buildx-action@v3
fails when append Buildx builder nodeLogs:
Expected behaviour
It should run successfully
Actual behaviour
It has cryptic error:
ERROR: failed to initialize builder builder-c0e8be7c-9e64-4e9f-ac0c-2d8d1aa68984 (builder-c0e8be7c-9e64-4e9f-ac0c-2d8d1aa6898[41](https://github.com/minswap/monorepo/actions/runs/12350039497/job/34462188386#step:5:42)): Get "http://docker.example.com/v1.47/containers/buildx_buildkit_builder-c0e8be7c-9e64-4e9f-ac0c-2d8d1aa689841/json": context deadline exceeded Error: Failed to append node undefined: ERROR: failed to initialize builder builder-c0e8be7c-9e64-4e9f-ac0c-2d8d1aa68984 (builder-c0e8be7c-9e64-4e9f-ac0c-2d8d1aa689841): Get "http://docker.example.com/v1.[47](https://github.com/minswap/monorepo/actions/runs/12350039497/job/34462188386#step:5:48)/containers/buildx_buildkit_builder-c0e8be7c-9e64-4e9f-ac0c-2d8d1aa689841/json": context deadline exceeded
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
No response
BuildKit logs
Additional info
No response
The text was updated successfully, but these errors were encountered: