Answers: <p>This has been a Docker bug caused by jumbo Ethernet frames while using VPN which has now been fixed. Thanks Docker team!</p>
  
  <p><a href="https://github.com/moby/moby/issues/34080" rel="nofollow noreferrer">https://github.com/moby/moby/issues/34080</a></p>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-17T13:00:00.170Z
Answers: 2017-08-17T13:00:00.170Z
Answers: Ta Mu
Answers: <p>You may wish to try disabling and uninstalling any antivirus software you have installed and see if it resolves the issue (I of course don't recommend this in the long term). I have seen two different instances of antivirus interrupting SSL conections on Windows 10 recently. Chrome would report a similar error to "bad record MAC" and the issue was generalized to any SSL website or connection and any browser. Unstalling or changing A/V software resolved the issue.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-07-12T21:03:46.480Z
Answers: Thx - I disabled all a/v services but w/o effect :/
Answers: Ta Mu
Answers: CC BY-SA 3.0
Answers: 2017-07-12T20:21:56.603Z
Answers: 2017-07-12T20:21:56.603Z
Answers: James Shewey
Body: <p>With a private registry, I cannot pull images because certains image layers fail to download. The pattern seems to be that this happens with larger, 50MB sized layers.
  It shouldn't be a registry neither network problem as colleagues with other systems manage to get these images.</p>
  
  <pre><code>6bbedd9b76a4: Pulling fs layer
  fc19d60a83f1: Download complete
  de413bb911fd: Download complete
  2879a7ad3144: Download complete
  668604fde02e: Download complete
  f257ac562635: Download complete
  07486ea9391a: Download complete
  c131a1091dea: Download complete
  e4e87f3caf2a: Downloading
  6ef05c7ca3e3: Retrying in 1 second
  85b7b45e23a1: Download complete
  077ff1474b65: Retrying in 1 second
  f85147a0e9d7: Waiting
  </code></pre>
  
  <p><a href="https://i.sstatic.net/dKRdS.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/dKRdS.png" alt="enter image description here"></a></p>
  
  <p>Other errors on new retries with same image:</p>
  
  <pre><code>2c1171c58a199d2ec9daee729d88146dfb91caba4788: local error: tls: bad record MAC
  
  error pulling image configuration: tls: received record with version 5ea7 when expecting version 303
  </code></pre>
  
  <p>UPD. Strange enough, the very first image layer which always gets stuck before it downloads anything stucks rarely at "downloading... 987B".</p>
  
  <p>UPD2. Same behaviour with Docker EE client (Docker-Client/17.03.0-ee-1)</p>
  
  <p>UPD3. Filed this as a <a href="https://github.com/moby/moby/issues/34080" rel="nofollow noreferrer">bug</a> to the Moby project.</p>
  
Comments: CC BY-SA 3.0
Comments: 2017-07-12T17:29:16.163Z
Comments: What Docker version are you using? Maybe related: https://github.com/nats-io/go-nats/issues/269
Comments: friism
Comments: CC BY-SA 3.0
Comments: 2017-07-12T17:32:19.830Z
Comments: @friism 
  interesting; so if I would increase TLS timeout how can I do that on Windows 10?! - 
  Docker version 17.06.0-ce, build 02c1d87
Comments: Ta Mu
Tags: <docker><windows>
Title: Strange behaviour of Docker CE/EE client on Windows - timeout for certain image layers
UserDisplayName: Ta Mu
ThreadText: # Strange behaviour of Docker CE/EE client on Windows - timeout for certain image layers
  
  (Asked by: username_0 on 2017-07-12)
  
  With a private registry, I cannot pull images because certains image layers fail to download. The pattern seems to be that this happens with larger, 50MB sized layers.
  It shouldn't be a registry neither network problem as colleagues with other systems manage to get these images.
  
  ```
  6bbedd9b76a4: Pulling fs layer
  fc19d60a83f1: Download complete
  de413bb911fd: Download complete
  2879a7ad3144: Download complete
  668604fde02e: Download complete
  f257ac562635: Download complete
  07486ea9391a: Download complete
  c131a1091dea: Download complete
  e4e87f3caf2a: Downloading
  6ef05c7ca3e3: Retrying in 1 second
  85b7b45e23a1: Download complete
  077ff1474b65: Retrying in 1 second
  f85147a0e9d7: Waiting
  
  ```
  
  [![enter image description here](https://i.sstatic.net/dKRdS.png)](https://i.sstatic.net/dKRdS.png)
  
  Other errors on new retries with same image:
  
  ```
  2c1171c58a199d2ec9daee729d88146dfb91caba4788: local error: tls: bad record MAC
  
  error pulling image configuration: tls: received record with version 5ea7 when expecting version 303
  
  ```
  
  UPD. Strange enough, the very first image layer which always gets stuck before it downloads anything stucks rarely at "downloading... 987B".
  
  UPD2. Same behaviour with Docker EE client (Docker-Client/17.03.0-ee-1)
  
  UPD3. Filed this as a [bug](https://github.com/moby/moby/issues/34080) to the Moby project.
  
  **Tags:** docker, windows
  
  > **Comments:**
  > **username_1**: What Docker version are you using? Maybe related: https://github.com/nats-io/go-nats/issues/269  
  > **username_0**: @username_1  interesting; so if I would increase TLS timeout how can I do that on Windows 10?! -  Docker version 17.06.0-ce, build 02c1d87  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2017-08-17. Score: 1 | Accepted answer
  
  This has been a Docker bug caused by jumbo Ethernet frames while using VPN which has now been fixed. Thanks Docker team!
  
  <https://github.com/moby/moby/issues/34080>
  
  
  ---
  
  ### Answer by username_2 on 2017-07-12. Score: 1
  
  You may wish to try disabling and uninstalling any antivirus software you have installed and see if it resolves the issue (I of course don't recommend this in the long term). I have seen two different instances of antivirus interrupting SSL conections on Windows 10 recently. Chrome would report a similar error to "bad record MAC" and the issue was generalized to any SSL website or connection and any browser. Unstalling or changing A/V software resolved the issue.
  
  > **Comments:**
  > **username_0**: Thx - I disabled all a/v services but w/o effect :/  
  
  ---
  
  