moby: Error pulling image configuration: connection reset by peer

Description

This has been reported multiple times already (#357, #2151, #4539, #5255, etc.) and has never been completely solved, it has just disappeared by itself. Since yesterday, some pull requests to docker registry fail with errors like error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/36/368db5c51bcd5821a9503b7d8349af948eaee516602969fe50915fd19f511cc0/data?Expires=1477399254&Signature=es6-HoHrzMRF1GtjFkiOq8E1aMlSMZzAwTWZuAI9DsRs-hJEdfRGoSYBBwSWxfzt2jZz0tySRfvpVSY8ef~wRwourd~QkA9G-sOf7ptk0B1FfWJLr7rlsmRSIpgF5sHMjkwxKTh~Tv-NzeDaEpMRMvm6fbMwjIJuZ~hKWZaH4z8_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: read tcp 10.0.2.15:35436->52.222.149.173:443: read: connection reset by peer

Steps to reproduce the issue:

1. Try to pull wordpress (latest). It will fail.

docker pull wordpress
Using default tag: latest
latest: Pulling from library/wordpress
43c265008fae: Pulling fs layer
6ee27d07994b: Pulling fs layer
d43536f442a0: Download complete
4d9469dadeb4: Waiting
4fc33aa1941b: Waiting
09b922600db1: Waiting
01805b6582a4: Waiting
ec43f09bb70c: Waiting
6568948eed6b: Waiting
2dc0094a10b5: Waiting
7142d56062ec: Waiting
7a44a9f63706: Waiting
9b7c9a7c3515: Waiting
59249fc11e6f: Waiting
31611c57ce32: Waiting
712c4eef2d95: Waiting
aaf3860b31ac: Waiting
b04c02901a3a: Waiting
eb9dd4eb321b: Waiting
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/36/368db5c51bcd5821a9503b7d8349af948eaee516602969fe50915fd19f511cc0/data?Expires=1477399254&Signature=es6-HoHrzMRF1GtjFkiOq8E1aMlSMZzAwTWZuAI9DsRs-hJEdfRGoSYBBwSWxfzt2jZz0tySRfvpVSY8ef~wRwourd~QkA9G-sOf7ptk0B1FfWJLr7rlsmRSIpgF5sHMjkwxKTh~Tv-NzeDaEpMRMvm6fbMwjIJuZ~hKWZaH4z8_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: read tcp 10.0.2.15:35436->52.222.149.173:443: read: connection reset by peer

1. Try to pull wordpress:4.3.1. It will take some time, but will eventually succeed (Some of the layers are going through one ore more retries).

 docker pull wordpress:4.3.1
4.3.1: Pulling from library/wordpress
d4bce7fd68df: Pull complete
a3ed95caeb02: Pull complete
77a07a807b0b: Pull complete
8e9dd06f34b8: Pull complete
bdeb40d51bd7: Pull complete
c1c9be13bf3c: Pull complete
b39c61dc46ac: Pull complete
7dd602b91016: Pull complete
523061e2010c: Pull complete
da8bdfcda793: Pull complete
0be8c57f353c: Pull complete
52c1189d4439: Pull complete
23ebc7f488dc: Pull complete
c2fadfc5c14d: Pull complete
08141e2af0f3: Pull complete
6f6c7167fd08: Pull complete
09fa28e1f215: Pull complete
fa2282b6ef71: Pull complete
8c2f663cf070: Pull complete

Describe the results you received: I have failed to pull a latest image from docker hub, however, I have successfully pulled not the latest tag for the same image. This also happens for other images and other tags.

Describe the results you expected: Obviously, I have expected to pull of the requested images.

Additional information you deem important (e.g. issue happens only occasionally): I have first discovered the issue yesterday, a few hours after I got Virtualbox updated to VirtualBox-5.0.28-111378-Win. The issue stayed after upgrading to VirtualBox-5.1.8-111374-Win and also stayed after upgrading docker toolbox to latest (v1.12.2). Also, I am testing this in an office with other coworkers that are not hitting the issue, but use similar setup (differences in OS and software version is possible).

Output of docker version:

Client:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 17:00:50 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 17:00:50 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.2
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 32
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge overlay null host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.24-boot2docker
Operating System: Boot2Docker 1.12.2 (TCL 7.2); HEAD : 9d8e41b - Tue Oct 11 23:40:08 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.9 MiB
Name: test-host-2
ID: QFKW:A5SR:LMSM:YO7X:GXTI:463S:4D2Q:OPRH:3TRX:KWK3:KNZA:6BVF
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 13
 Goroutines: 23
 System Time: 2016-10-25T12:39:27.186690998Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Insecure Registries:
 127.0.0.0/8

Additional environment details (AWS, VirtualBox, physical, etc.): Virtualbox on Windows. See used versions in the text above.