Docker Community Forums

Share and learn in the Docker community.

Docker pull freezes after several files

Using Docker version 20.10.0, build 7287ab3

Pulling a small container like hello-world works, but pulling something like node freezes after several files load.
So far tried:

  1. Restarting Docker
  2. WSL shutdown
  3. Docker reinstall
  4. Disabling windows firewall
  5. Adding Dns resolution via google 8.8.8.8 in docker config
  6. Shutting down VPN, stopping mcafee antivirus
  7. Limiting the max-number of downloaded files to - 1 at a time, on docker configuration (Suggested on these forums).
  8. Cleaned the cache
    Any suggestions?
    The trouble is with the udp connection that is closing. I’ll Add the docker log here:

[16:58:14.593][WslIntegrationAgent-Ubuntu-20.04][Info ] msg=“proxy >> POST /v1.41/images/create?fromImage=node&tag=latest\n”
[16:58:14.649][VpnKit ][Info ] vpnkit.exe: Connected Ethernet interface f6:16:36:bc:f9:c6
[16:58:14.649][VpnKit ][Info ] vpnkit.exe: UDP interface connected on 3.218.162.19
[16:58:15.398][VpnKit ][Info ] vpnkit.exe: Connected Ethernet interface f6:16:36:bc:f9:c6
[16:58:15.398][VpnKit ][Info ] vpnkit.exe: UDP interface connected on 52.4.20.24
[16:58:17.562][VpnKit ][Error ] vpnkit.exe: Socket.TCPv4.write tcp:3.218.162.19:443: caught Bad file descriptor returning Eof
[16:58:17.703][VpnKit ][Info ] vpnkit.exe: Connected Ethernet interface f6:16:36:bc:f9:c6
[16:58:17.704][VpnKit ][Info ] vpnkit.exe: UDP interface connected on 104.18.121.25
[17:01:49.130][VpnKit ][Info ] vpnkit.exe: Max retransmits reached for connection - terminating
[17:04:07.194][VpnKit ][Warning] vpnkit.exe: TCP 192.168.65.3:56154 > 104.18.121.25:443 closing flow due to idle port disconnection

I see the same issue. Is there anyway this can be fixed?

same here, nothing help.
please can we get any input about this one?

I am facing same issue, Please update if anyone solved same.

Found a solution.
Install Ubuntu On Hyper-v
Install docker on Ubuntu
Everything works,
Dump Docker Desktop on WSL2 - it’s currently not working on some machines