Eventual certain loss of network connectivity

[GameFuzzy]

• [x] I have tried with the latest version of Docker Desktop
• [x] I have tried disabling enabled experimental features
• [x] I have uploaded Diagnostics
• Diagnostics ID: B7299C12-4F44-4F62-8DBC-653C27DD8723/20230505205538

Actual behavior

After a seemingly arbitrary amount of time that can range from anywhere between 10 minutes to 48 hours-ish, all requests sent from my Docker containers to the outside world suddenly start timing out like this:

docker run --rm --network=host busybox traceroute 192.168.1.145
traceroute to 192.168.1.145 (192.168.1.145), 30 hops max, 46 byte packets
 1  192.168.65.5 (192.168.65.5)  0.011 ms  0.008 ms  0.008 ms
 2  192.168.65.3 (192.168.65.3)  3109.999 ms !H  3060.012 ms !H  3119.841 ms !H

Expected behavior

Hosts outside the internal Docker network are reachable.

Information

• Is it reproducible? Yes
• Is the problem new? No. Though I've only been using Docker for Windows for a few weeks at this point.
• Did the problem appear with an update? No

What I've tried:

• I've checked to make sure it's not a DNS issue by pinging 8.8.8.8 as well as local addresses, neither of which resolve.
• I've tried changing the "bip" value in the Docker daemon config to "192.168.200.1/24" to make sure it's not conflicting with anything.

The only "fix" I've been able to come up with is restarting the Docker engine every time it happens, which is extremely tedious since I also have to restart WSL due to Docker breaking my VHD mount points. See #9364.

I should probably also add that the internet connectivity on my main WSL distro is completely unaffected by this issue.

Version information

• Windows Version: Windows 11 Pro x64 21H2 (22000.1817)
• Docker Desktop Version: 4.18.0 (104112)
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

https://pastebin.com/23cXujQX

Steps to reproduce the behavior

1. Start Docker Desktop
2. Start containers
3. Wait until all services running in your containers that rely on being able to connect to anything besides the internal Docker network suddenly stop working (or try pinging 8.8.8.8 from inside any container).

[Bastien42]

can confirm that the same issue is happening on Docker Desktop 4.19.0 (106363)

Windows Version: Windows 11 Pro x64 22H2 (22621.1555) Docker Desktop : 4.19.0 (106363) WSL2 or Hyper-V backend? WSL2 Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

[rishi003]

Has anyone found a resolution for this?

[cvietor]

+1 same issue here