Repository navigation
[BUG] Docker Labspaces not working #13879
Description
Description
I execute any lab in labspaces and returns proxyconnect tcp: open ./pipe/dockerHttpProxy: The system cannot find the path specified.
I don't have proxy in my machine and deactivate this in settings, how do I resolve it? with proxy in system returns the same error
Steps To Reproduce
time="2026-06-26T11:29:09-03:00" level=info msg="fetch failed" error="failed to do request: Head \"https://registry-1.docker.io/v2/dockersamples/labspace-content-dev/manifests/latest\": proxyconnect tcp: open ./pipe/dockerHttpProxy: The system cannot find the path specified." host=registry-1.docker.io spanID=3083559c30688970 traceID=2bc444f56044c5c6b082bf46944091c7 failed to pull OCI resource "docker.io/dockersamples/labspace-content-dev:latest": failed to do request: Head "https://registry-1.docker.io/v2/dockersamples/labspace-content-dev/manifests/latest": proxyconnect tcp: open ./pipe/dockerHttpProxy: The system cannot find the path specified.
Compose Version
Docker Compose version v5.1.4
Docker Environment
Client:
Version: 29.5.3
Context: default
Debug Mode: false
Plugins:
agent: Docker AI Agent Runner (Docker Inc.)
Version: v1.79.0
Path: C:\Program Files\Docker\cli-plugins\docker-agent.exe
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.25.0
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.34.1-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v5.1.4
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.47
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Docker Inc.)
Version: v0.4.1
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
dhi: CLI for managing Docker Hardened Images (Docker Inc.)
Version: v0.0.4
Path: C:\Program Files\Docker\cli-plugins\docker-dhi.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.31
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
mcp: Docker MCP Plugin (Docker Inc.)
Version: v0.42.2
Path: C:\Program Files\Docker\cli-plugins\docker-mcp.exe
model: Docker Model Runner (Docker Inc.)
Version: v1.2.1
Path: C:\Program Files\Docker\cli-plugins\docker-model.exe
offload: Docker Offload (Docker Inc.)
Version: v0.6.4
Path: C:\Program Files\Docker\cli-plugins\docker-offload.exe
pass: Docker Pass Secrets Manager Plugin (beta) (Docker Inc.)
Version: v0.1.5
Path: C:\Program Files\Docker\cli-plugins\docker-pass.exe
sandbox: Docker Sandbox (Docker Inc.)
Version: v0.12.0
Path: C:\Program Files\Docker\cli-plugins\docker-sandbox.exe
scout: Docker Scout (Docker Inc.)
Version: v1.22.0
Path: C:\Users\tatia\.docker\cli-plugins\docker-scout.exe
Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 4
Server Version: 29.5.3
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Discovered Devices:
cdi: docker.com/gpu=webgpu
Swarm: active
NodeID: jq78oheqafeb0pldbsw3gyt51
Is Manager: true
ClusterID: ijtqwc46iwqe35h8aac5v7pc9
Managers: 1
Nodes: 1
Data Path Port: 4789
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 192.168.65.3
Manager Addresses:
192.168.65.3:2377
Runtimes: io.containerd.runc.v2 nvidia runc
Default Runtime: runc
Init Binary: docker-init
containerd version: e53c7c1516c3b2bff98eb76f1f4117477e6f4e66
runc version: v1.3.6-0-g491b69ba
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.18.33.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 5.788GiB
Name: docker-desktop
ID: af620ec0-a368-487c-9cd6-8be4f024a0b0
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=npipe://\\.\pipe\docker_cli
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
::1/128
127.0.0.0/8
Live Restore Enabled: false
Firewall Backend: iptables
Anything else?
No response
Activity
glours commentedon Jun 26, 2026
@pachecotatih @wegurecocuca17 you can use Compose
v5.2.0, which proposes a fix to this issue and if you're facing same kind of problem during the auth, try to build a custom version of Compose from the main branch. I opened a PR a few days ago that should fix the issue.glours commentedon Jul 7, 2026
@pachecotatih @wegurecocuca17 Compose v5.3.0 should fix your issue. Let me know if that’s not the case, and please provide a reproducible test case if the issue still happens.
glours commentedon Jul 21, 2026
Closing this issue as we haven't received a response from the reporters within a reasonable delay, as per our contribution guidelines.
On our side, we also received internal feedback from customers confirming that this issue is fixed by Compose
v5.3.0.If you're still experiencing this problem with the latest version of Compose, feel free to comment with a reproducible test case and we'll reopen the issue.