GWSL-Source VS WSLHostPatcher

That vsock thing can be done with GWSL/VcXsrv too. Check this out: https://github.com/nbdd0121/wsld

Install an X server in Windows (that page mentions VcXsrv and/but I recommend GWSL which also uses VcXsrv for a little nicer experience).

and GWSL https://github.com/Opticos/GWSL-Source with settings:

With OpenInWSL, possibly using alonside GWSL.

I don't know but if all you want is a working X server and you don't need Xming specifically then give GWSL/VcXsrv a try instead.

You may instead want to use an X server and I recommend GWSL for that.

I don't feel like troubleshooting that issue any further so if all you needed was GUI app support and not necessarily GPU compute capabilities (CUDA etc) then use this: https://opticos.github.io/gwsl/.

Also, if for some reason you decide that you aren't big on the idea of Wayland yet (as in if you don't have a care for the Wayland features and/or WSLg's PCIe partitioning based direct GPU access etc) then you can opt to disable the guiApplications setting in your .wslconfig file and instead install an X server (like VcXsrv, or GWSL that uses it and provides some nice to have GUI controls etc for it) and be able to set your preferred titlebar/border via the said themes from Pling etc from within your WSL distro environments themselves (install lxappearance or GNOME Tweaks Tool to set them up).

Yeah, all of that seems to be available if you use WSL1 and pair it up with an X server (GWSL is a handy FOSS package for that and the dev's OpenInWSL app makes the integration even more seamless).

I had the same problem actually, you need this https://github.com/CzBiX/WSLHostPatcher and just run it under windows, the you need to tell metro to listen to you pc/laptop’s network address

WSL provides a great environment for web developers working on Windows. However, it's not always easy to access the applications running in WSL from the local network. Whether you're working on a web app, a React-Native application, REST API, or have a database residing in a Docker container, you'll need to access it from a real mobile phone or simply from a different device. While there are ways to achieve this, they are not always easy to implement. Some of them require tackling with an NIC Bridge mode or manually downloading and applying a WSLHostPatcher. Which are things you probably don't want to deal with when you're just trying to get your work done. Here's where Expose-WSL comes into play.

So, then your options are: 1) a real HTTP (reverse) proxy like Apache or nginx on Windows, 2) changing your VM network to bridge mode and manually configuring an address every time you start WSL2 (https://stackoverflow.com/a/62438375 , see "option 2"), or maybe 3) https://github.com/CzBiX/WSLHostPatcher this thing

Try this app: https://github.com/CzBiX/WSLHostPatcher. I've checked the code and it isn't harmful at all, it just checks for any wslhost.exe's created connections after the .EXE is run (by just using hooks) and makes it so they listen on all interfaces instead of just localhost, so this effectively makes your WSL2 and Windows listening connections to be merged together in the same network stack, to say it that way. Or in other words, dynamic port forwarding.

This looks good https://github.com/CzBiX/WSLHostPatcher but that’s for tomorrow!