It's been a year but if I recall it went something like this:
I was using microk8s (a kubernetes distribution) on the wsl side, and I had python scripts (also on the wsl side) which would deploy things into it, run tests until there was a problem, forward a port from the broken service to "localhost:8080", and then instruct the user to open a browser to explore the UI post-test-failure.
On bare metal Linux this was no big deal because "localhost" was unambiguous. But on windows you end up with the browser on the windows side and the forwarded port on the wsl side, so when the browser opened there was nothing at "localhost:8080" even though I could "curl localhost:8080" from the wsl side and get a response.
Presumably there is a way to further forward the port so that it is available to both Windows browsers and wsl python scripts, but I never found it.
I was using microk8s (a kubernetes distribution) on the wsl side, and I had python scripts (also on the wsl side) which would deploy things into it, run tests until there was a problem, forward a port from the broken service to "localhost:8080", and then instruct the user to open a browser to explore the UI post-test-failure.
On bare metal Linux this was no big deal because "localhost" was unambiguous. But on windows you end up with the browser on the windows side and the forwarded port on the wsl side, so when the browser opened there was nothing at "localhost:8080" even though I could "curl localhost:8080" from the wsl side and get a response.
Presumably there is a way to further forward the port so that it is available to both Windows browsers and wsl python scripts, but I never found it.