WSL: Docker pull error with Surface Dock "bad record MAC"

  • Your Windows build number: 19018.1

  • What you’re doing and what’s happening:
    WSL2 Ubuntu on a Surface Book connected to a Surface Dock with hardwired network connection through the dock (Surface Ethernet Adapter). When I run docker pull ubuntu, the result is local error: tls: bad record MAC and image isn’t downloaded.

Unplugging network cable from the Surface Dock and using wireless, docker pull works fine. Using a different network adapter through USB and going through that wired connection, docker pull works fine. Error only results when using the network connection in the Surface Dock.

Similar to this and this issue, but now with a wired connection instead of wireless. I checked if there is a firmware update for the Dock and it’s already on the latest (1.42.139) according to this doc.

Comparing network connection properties between the two ethernet connections, I don’t see a difference.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 1
  • Comments: 15 (1 by maintainers)

Most upvoted comments

had the same problem, switched from 2.4Ghz to 5.0Ghz and it works. don’t know if is due to that

I don’t think this is a Surface Dock problem… I’m struggling with this error since months and have to retry docker pulls and apt-get installs several times until everything goes through. Only on this one PC… it’s got some ASRock Z170 Extreme4 board and a “AVM FRITZ!WLAN Stick AC 860” Wifi adapter, all with latest drivers.

I’m not sure if it’s a driver / NIC problem - I can curl debian isos day and night without a single error on Windows/PowerShell and in WSL2/Ubuntu/bash - but I get “bad record mac” errors when I try to curl the same debian iso in a docker container or when I try to docker pull something.

image

It isn’t that no one wants to fix it. There’s no repro; or, at least, no flood of Surface Book users (of which, let’s assume there are a few at MSFT) rushing to thumbs up the OP. The error strongly suggests (but does not prove) an unidentified external factor vs. something plausibly actionable within WSL.

This issue isn’t a dup of 4306

That’s fair. Your poison on open/closed status.

Other reports suggest it was a driver/NIC issue. https://github.com/microsoft/WSL/issues/4306