The ip from /etc/nf can be pinged, but windows programs/services are not listening to it it seems, even though they're bound to 0.0.0.0. I am observing that the ip in /etc/nf is always different from what is resolving to. Those are not working, it seems you really need to shutdown wsl to get it to regenerate the correct ip mapping. Sounds easy afterwards, but if you don't know how this works under the hood it can take you a lot of time to find out. What worked for me today is wsl -shutdown. Delete the old network sudo service docker stop sudo ip link set dev docker0 down sudo brctl delbr docker0 2. Ideally the network change gets picked up so the DNS / host entry for gets updated.ĭocument this usecase by explaining the steps needed to get working again. This article introduces two methods to modify the default bridge of docker, both of which are realized by modifying the daemon.json file.First kind 1. So everything relying on for connectivity to the windows host will fail. But WSL2 (or docker for win) isn't aware of this or reacting to it.
When changing networks, for example disconnecting my laptop from the docking, should update the ip mapping and possibly other entries like those in /etc/nfĬurrently when undocking, my laptop switches to WiFi, which is to be expected. Is your feature request related to a problem? Please describe. Therefore, all our own installed software and deployed business projects use our own network. This network can only be accessed through the IP of the container, not through the container name. Forgive if this has been reported / discussed / documented somewhere, but I couldn't find it. Docker installs redis and starts it as a configuration file.