-
Notifications
You must be signed in to change notification settings - Fork 481
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
Error using buildx create using the default docker context with TLS #2520
Comments
@chrisbecke Can you show the output of Edit: I can find it with
|
Similar to docker/setup-buildx-action#105 (comment), you need to create a context for current environment when current context has TLS data loaded and set the endpoint when creating the builder. With your example: volumes:
certs:
services:
docker:
image: docker:dind
privileged: true
volumes:
- certs:/certs
cli:
image: docker:cli
depends_on:
- docker
volumes:
- certs:/certs
|
There is no dispute that the workaround is easy :- in the context of CI pipelines however it becomes messy as it adds another unexpected failure mode when (trying) to update from an unencrypted to a tls based docker:dind connection. |
Contributing guidelines
I've found a bug and checked that ...
Description
ERROR when calling
docker buildx create
using the default, docker context with a TLS protected docker socket.Expected behaviour
Actual behaviour
Buildx version
github.com/docker/buildx v0.14.1 59582a8
Docker info
Builders list
Configuration
compose.yaml
compose.yaml
Build logs
Additional info
No response
The text was updated successfully, but these errors were encountered: