x11docker VS ContainerBox

I don't know anything about Xwayland, but according there's this sentence in this socat writeup:

> If you want to access an X server that does not provide -listen tcp (Xwayland) or just did not have enabled it during startup (like most likely your host Xorg), you can use socat to provide TCP/IP access.

https://github.com/mviereck/x11docker/wiki/How-to-access-X-o...

I've run into this before, but I never ended up using it: https://github.com/mviereck/x11docker

I managed to “fix” the error log messages by following this guide: https://github.com/mviereck/x11docker/wiki/How-to-connect-container-to-DBus-from-host

at least, I'd suggest you take a look at https://github.com/mviereck/x11docker/issues/418

x11docker would be a good starting point to see what is possible: https://github.com/mviereck/x11docker and in particular https://github.com/mviereck/x11docker/wiki/Display-manager-entry-for-x11docker .

Instead of using a homegrown solution, check out x11docker. It attempts to safely allow you to use x inside a container. There are certain cases where a malicious actor could take over your computer if you don't mount the relevant things safely.

This is what I use x11docker for!

It's straighforward to have your container talk to Xorg directly but for a better experience take a look at https://github.com/mviereck/x11docker as it does the heavy lifting regarding GPU, sounds, devices, etc.

The solution I'm currently checking is ContainerBox (https://github.com/AlexandreDey/ContainerBox). I'm building a container for KDE and I'll get back with results.