5 minutes delay when executing docker pull/docker manifest commands

[kakuzei]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: AA543B89-A14B-4EA0-8D2C-1695EC1DDB25/20230116084533

Actual behavior

When I execute a docker pull or a docker manifest command, the command takes almost 5 minutes to be executed instead a few seconds:

user@host:~> time docker pull hello-world
Using default tag: latest
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:aa0cc8055b82dc2509bed2e19b275c8f463506616377219d9642221ab53cf9fe
Status: Downloaded newer image for hello-world:latest
docker.io/library/hello-world:latest

real    5m01.117s
user    0m0.071s
sys     0m0.019s

Expected behavior

I expect the docker pull hello-world command to be executed in few seconds.

Information

I'm having the following issue with Docker Desktop (4.16.1) on Windows 10 (10.0.19044.2486) from a WSL2 Ubuntu 22.04.1 LTS VM using the WSL Integration:
When I execute a docker pull or a docker manifest command from the Ubuntu VM, I'm observing this:

• There are 2 DNS resolution requests executed to resolve the name of the Docker registry: one for type A and one for type AAAA
• The responses for these 2 requests come very quickly (less than 1 second later)
• After that, there is a delay of 5 minutes
• Then they are 2 or 3 DNS resolution requests executed: one for the type A and 1 or 2 for the type AAAA,
• When the responses for these 2 or 3 more requests are received: the next step of the docker command is executed well, without any unexpected delay.

This issue is causing a lot of trouble to my team since the beginning of the year.

After some research on my side, it looks like when I remove the Windows KB5021233 December Security patch, I don't have the 5 minutes delay anymore but 5 seconds instead.
When I run the same kind of command directly from Windows or from the Ubuntu VM using dockerd, there is no 2 steps of DNS resolution requests and no 5 seconds or 5 minutes delay.

We opened a ticket to the WSL support here: microsoft/WSL#9461
I really think they introduced an issue with the KB5021233 but it seems to just highlight the latency between the 2 steps of DNS resolution requests which increase from 5 seconds to 5 minutes.

Why there is 5 minutes delay when I use Docker Desktop from the Ubuntu VM using the WSL integration?

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

com.docker.diagnose.exe check
[2023-01-16T08:38:45.823853900Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
No fatal errors detected.

[kakuzei]

This issue has been solved, more details here: #10247 (comment)

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked