Docker Community Forums

Share and learn in the Docker community.

Docker Pull on Windows 2016 is Freezing/Stalling (TCP errors)

docker
dockerhub

(Tresstylez) #1

I’m trying to pull the microsoft/iis image from the Docker registry and the pull partially completes before it completely freezes, retries, then eventually times out. Typically it has this error:

read tcp 10.10.3.92:50583->72.21.81.200:443: wsarecv: An existing connection was forcibly closed by the remote host.

Also, I’ve seen this:

dial tcp: lookup index.docker.io: no such host

This Docker Host is running on a Windows 2016 Server Core VMWare VM, and Docker was installed using the Quick Start Guide.

Any help is appreciated!


PS D:\ProgramData> docker info
Containers: 1
_ Running: 0_
_ Paused: 0_
_ Stopped: 1_
Images: 1
Server Version: 17.03.0-ee-1
Storage Driver: windowsfilter
_ Windows:_
Logging Driver: json-file
Plugins:
_ Volume: local_
_ Network: l2bridge l2tunnel nat null overlay transparent_
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 14393 (14393.953.amd64fre.rs1_release_inmarket.170303-1614)
Operating System: Windows Server 2016 Standard
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 16 GiB
Name: SJDOCKERWINCORE
ID: 7CA7:33BK:AFZA:LTBS:B7MP:V2BN:6TSA:EG5D:L7PL:YO6M:E44C:QHI2
Docker Root Dir: D:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
_ 127.0.0.0/8_
Live Restore Enabled: false



(Umerjafer) #2

I am also facing this problem. Everything for working fine a few weeks ago but recently I am getting the following error

read tcp xxx.xxx.xxx.xxx:11421->204.79.197.219:443: wsarecv: An existing connection was forcibly closed by the remote host

I tried to browse 204.79.197.219 and I found the following:

Our services aren’t available right now

We’re working to restore all services as soon as possible. Please check back soon.

Ref A: C5B7936B4E80484EB0504EB0FAEAC266 Ref B: MRS01EDGE0104 Ref C: 2018-11-01T11:30:01Z

This has been happening for more than a week now and I am not sure where to pull the image from.