Restart WSL/Docker daemon, notice that the connection is suddenly more reliable though it will begin to deteriorate over time again.Check back in a day to see if the connection is timing out more frequently.Poll this application from within a Docker container inside a Docker bridge network living within WSL2.Run an application on the Windows host.I have had this problem ever since starting to use Docker for Windows with the WSL2 backend. Are you running inside a virtualized Windows e.g.It just starts timing out more and more often the longer the network/containers have been up. It may be related to the overall network issues linked above.
Shifting applications out of Docker and onto the host fixes their communication issues as well. Running wsl -shutdown and restarting the Docker daemon fixes the issue temporarily.
When launching WSL, the applications are able to communicate reliably, but this connection deteriorates over time, and after 1-2 days, I notice frequent connection timed out responses from the application running on the host. I have multiple applications inside Docker containers running inside a Docker bridge network that poll this application every few seconds. I would expect services running inside Docker containers in a WSL backend to be able to reliably communicate with applications running on the host, even with frequent polling Actual behaviorĭue to #8590, I have to run some applications that require high download speeds on the host. I have tried with the latest version of my channel (Stable or Edge).
0 kommentar(er)
