Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) 错误代码: E_FAIL

[m178520]

Windows Version

Windows 10.0.22631.6199

WSL Version

wslc 2.9.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

Repro Steps

I'm a developer from China. Seeing that our wsl supports directly starting containers, I immediately went to check it out. As a result, the following error occurred when pulling the image.

wslc run --rm -it ubuntu:latest bash -c "echo Hello world from WSL container!"

Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
错误代码: E_FAIL

Expected Behavior

It is hoped that we can change the source of the image we pull like docker does, so as to prevent such errors from happening

Actual Behavior

Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
错误代码: E_FAIL

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[m178520]

/feature   2668350209 ***@***.***  

…

------------------ 原始邮件 ------------------ 发件人: ***@***.***>; 发送时间: 2026年7月5日(星期天) 凌晨4:14 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [microsoft/WSL] Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) 错误代码: E_FAIL (Issue #40995) github-actions[bot] left a comment (microsoft/WSL#40995) Logs are required for review from WSL team If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine. How to collect WSL logs Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt: Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 The script will output the path of the log file once done. If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues Once completed please upload the output files to this GitHub issue. See Collect WSL logs (recommended method). If you choose to email these logs instead of attaching them to the bug, please send them to ***@***.*** with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'
Found '/feature', adding tag 'feature'
Found '/emailed-logs', adding tag 'emailed-logs'

[OneBlue]

@m178520: What do you mean by "changing the source ?" Do you mean to download an image from a private registry, or have a mirror for the default registry ?