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
..
desktop	fix: route OCI artifact pulls through Docker Desktop HTTP proxy	2026-05-18 10:53:23 +02:00
experimental	next release will be major version v5.x	2025-11-13 09:32:43 +01:00
locker	use new moby/moby modules instead of docker/docker dependency	2026-04-08 08:50:50 +02:00
memnet	feat(desktop): add Docker Desktop detection and client skeleton (#11593)	2024-03-12 09:47:41 -04:00
oci	fix: route OCI artifact pulls through Docker Desktop HTTP proxy	2026-05-18 10:53:23 +02:00
paths	use go-compose instead Signed-off-by: tensorworker <tensorworker@proton.me>	2026-01-15 08:24:20 +01:00
pidfile	use new moby/moby modules instead of docker/docker dependency	2026-04-08 08:50:50 +02:00
registry	use containerd registry client	2025-09-26 18:45:07 +02:00
sync	test: migrate tar_test.go from testify to gotest.tools/v3	2026-04-03 12:29:07 +02:00
tracing	feat: add Docker Desktop Logs view hints and navigation shortcut	2026-04-10 15:26:08 +02:00
variables.go	format code with gofumpt	2024-12-17 16:50:14 +01:00