-
Notifications
You must be signed in to change notification settings - Fork 1.2k
buildctl attempts to use configured HTTP_PROXY/HTTPS_PROXY for local unix:// address #6002
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
Comments
🤔 I can't reproduce this.
|
Hi,
networks:
default:
services:
proxy:
image: ubuntu/squid
networks:
- default
expose:
- 3128
buildkit:
image: moby/buildkit@sha256:bd26cba1017fc236480bc4ecc0da799a6ad550d481c50bafe5fb468bd50c83a5
privileged: true
networks:
- default
environment:
- HTTP_PROXY=http://proxy:3128
- HTTPS_PROXY=http://proxy:3128
- http_proxy=http://proxy:3128
- https_proxy=http://proxy:3128
- NO_PROXY=127.0.0.0/8,::1,localhost
- no_proxy=127.0.0.0/8,::1,localhost
- BUILDKIT_HOST=unix:///run/buildkit/buildkitd.sock
- DOCKER_CONFIG=/root/.docker/
volumes:
- ./config.json:/root/.docker/config.json
entrypoint: ["buildkitd"]
command: ["--allow-insecure-entitlement=network.host", "--allow-insecure-entitlement=security.insecure", "--addr=unix:///run/buildkit/buildkitd.sock"]
Exec:
Squid log:
EDIT: Also seems to happen if I don't mount the
|
Contributing guidelines and issue reporting guide
Well-formed report checklist
Description of bug
Bug description
It seems that buildctl now attempts to to use the configured proxy for connections to
unix://
addresses which results in proxy errors as they can not reach a local socket address. I am not sure if aunix://
could ever be reached via proxy and this is intended behavior but I would assume that the proxy should only be used fortcp://
style addresses.Reproduction
Running buildctl with a configured proxy results in an error response from the proxy being printed with it being unable to find the requested address.
As a workaround / as verification that it is proxy related:
Setting
.sock
as a no proxy domain results in buildctl functioning like normal.Version information
According to our CI pipelines this change was introduced sometime after:
The text was updated successfully, but these errors were encountered: