-
Notifications
You must be signed in to change notification settings - Fork 293
Daemon: proxy connection refused - using system proxy in Windows #14706
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
It happened to me, too. (HTTP code 500) server error - Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 127.0.0.1:1080: connect: connection refused |
The same issue after upgraded Docker Desktop to 4.40.0. |
The same to me, i can curl but docker proxy is error
|
I remove the wsl config |
The same to me. After I remove the wsl config |
Same here. |
thanks, it works! |
Thanks, it works too |
Description
Daemon returns an error when I am using commands like
docker search
anddocker pull
. Daemon cannot connect to the system proxy.Reproduce
mirrored
.docker search alpine
in Powershell.Expected behavior
No response
docker version
Client: Version: 28.0.4 API version: 1.48 Go version: go1.23.7 Git commit: b8034c0 Built: Tue Mar 25 15:07:48 2025 OS/Arch: windows/amd64 Context: desktop-linux Server: Docker Desktop 4.40.0 (187762) Engine: Version: 28.0.4 API version: 1.48 (minimum version 1.24) Go version: go1.23.7 Git commit: 6430e49 Built: Tue Mar 25 15:07:22 2025 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.7.26 GitCommit: 753481ec61c7c8955a23d6ff7bc8e4daed455734 runc: Version: 1.2.5 GitCommit: v1.2.5-0-g59923ef docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
E08A41C0-0C5E-4F80-9481-CC3AADA6DF29/20250404132805
Additional Info
This issue seems to be related to the mirrored mode of WSL networking. After enabling mirrored mode in WSL network settings, WSL automatically sets variables like
HTTP_PROXY
in all distros including docker-desktop and I cannot modify them by editingdaemon.json
or setting Resources->Proxies in Docker Desktop settings.The connection error seems only to happen in the daemon process, but not in the whole docker-desktop WSL distro environment. The following commands are executed in the docker-desktop WSL distro.
The text was updated successfully, but these errors were encountered: