x11docker: WSL2 + Windows Not Working

I currently have been having non-stop issues on my Windows 10 machine, although this works near flawlessly on Linux.

After installing x11docker in WSL2 (Ubuntu 20.04 LTS), and installing VcXsrv on Windows. When launching any application (like telegram desktop, chromium, any example on the README.md) that the VcXsrv server starts on Windows, has a random port and then will close/shut down, and inside of WSL2 returns back to CLI. Before I was getting an error about could not connect to X server, and now not even that happens.

[173:173:0221/040852.601553:ERROR:browser_main_loop.cc(1438)] Unable to open X display when trying to launch chromium gets printed on the WSL2 command line.

If I use XLaunch and leave the server open, I don’t see any way to provide which display to try and connect to (it always starts a new one with runx). There are no errors, or logs anywhere so I’m kind of at a loss on what to do next.

Is there a way to provide the display number instead of launching a new one to runx? I’ll be happy to provide any additional details, but here’s the generic “dump” of information.

And I know that support for WSL2 is iffy, but hopefully I can help find a solution, but if not I can always run a VM 😃

Windows 10 20H2 (OS Build 19042.804)

No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal

x11docker --version 6.6.2

runx version v0.4.2

vcxsrv-64.1.20.9.0

Firewall: Off (for testing)/VcXsrv was added