Closed cody-scott closed 1 year ago
@namur007 Were you able to resolve this issue?
I actually did. My situation turned out to be related to the windows service OpenSSH Authentication Agent
. For some reason it was in manual mode. Once i swapped it to automatic (and rebooted) it has worked fine ever since.
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked
Actual behavior
running
docker pull hello-world
results inError response from daemon: Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout
from the client within WSL2. Following this, some websites become unreachable from my windows host.docker pull hello-world
performs as expected from powershell in windows. Image pulls successfully.curl -iv https://registry-1.docker.io/v2/
from WSL2 container to docker results in successful connections and response.I have a suspicion it is related to VPNKit or something with how its delivering the request back to the host machine from docker. My initial guess was MTU related, but setting all MTU values to be a smaller number (
1200
) still results in the same error behaviour. Success in windows, fail in WSL2, broken network.My other guess was it something related to TLS1.2 vs 1.3. From windows docker is negotiating 1.2, but its unclear what WSL2 is trying to do (1.3 or 1.2). Enabling 1.3 in internet settings results in no change.
Wireshark shows
Incomplete. ESTABLISHED (7)
. so it looks like its at least getting started, but then fails.Time is also in sync between the host/vm.
Expected behavior
successful pull of the image from docker to WSL2 machine
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check