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 <[email protected]>

2026-05-18 10:53:23 +02:00

..

cache_darwin.go

add a copyright notice with original author

2023-11-02 11:16:35 +01:00

cache_unix.go

feat(os): add FreeBSD support

2025-07-11 10:44:45 +02:00

cache_windows.go

add a copyright notice with original author

2023-11-02 11:16:35 +01:00

cache.go

re-implement cache folder detection

2023-11-02 11:16:35 +01:00

git_test.go

fix(git): Add validation for Git subdirectory paths to prevent traversal

2025-10-30 10:08:29 +01:00

git.go

golangci-lint: use gci formatter instead of goimports

2025-12-01 12:21:50 +01:00

oci_test.go

Test to check writeComposeFile detects invalid OCI artifact

2025-10-22 20:09:32 +02:00

oci.go

fix: route OCI artifact pulls through Docker Desktop HTTP proxy

2026-05-18 10:53:23 +02:00