compose/internal/oci
Guillaume Lours 66c21c3b6c fix: route OCI artifact pulls through Docker Desktop HTTP proxy
The compose process performs OCI artifact fetches in-process via
containerd's docker resolver, whose default transport only honors
HTTP_PROXY/HTTPS_PROXY/NO_PROXY env vars. Users behind PAC-only
corporate proxies hit i/o timeouts on `oci://` includes and on
`compose publish`.

When Docker Desktop is the active engine and exposes httpproxy.sock,
route the resolver through it (PAC-aware). Falls back to the default
transport when DD is unavailable or the socket is missing. Modeled on
docker/mcp-gateway PR #354.

Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
2026-05-18 10:53:23 +02:00
..
push.go golangci-lint: use gci formatter instead of goimports 2025-12-01 12:21:50 +01:00
resolver.go fix: route OCI artifact pulls through Docker Desktop HTTP proxy 2026-05-18 10:53:23 +02:00
resolver_test.go fix: route OCI artifact pulls through Docker Desktop HTTP proxy 2026-05-18 10:53:23 +02:00