I’ve seen this but I don’t really want the docker part.
I think it could be phenomenal for some kind of beefy VDI implementation for low demanding games or some kind of monster server with multiple GPUs, but it just feels wrong for an individual who wants to remotely stream their desktop on demand and has no plans on having others share the host.
Maybe i’m overthinking it, or haven’t thought it through enough - but my gut says this has more drawbacks than i’m realizing.
I’m in search for the same white whale. There’s quite a bit of documentation for multi-seat configurations for Linux, i.e. supporting the use of multiple screens and keyboards for separate simultaneous logins.
However I’d like to remote into a separate game scope session with its own human interface inputs and virtual audio and video outputs, as the same primary user normally logged in active desktop environment session. I’d like it so the remote and local sessions would not interfere with each other state, but without necessitating multiple Linux users for each session use case.
That last bit is what makes it more tricky and very niche. Supporting essentially multiple desktop environments probably demands separate user debus sockets. Using c groups via containers makes that viable, but like you, I also like to avoid containers and extensive volume mounts.
I’ve seen this but I don’t really want the docker part.
I think it could be phenomenal for some kind of beefy VDI implementation for low demanding games or some kind of monster server with multiple GPUs, but it just feels wrong for an individual who wants to remotely stream their desktop on demand and has no plans on having others share the host.
Maybe i’m overthinking it, or haven’t thought it through enough - but my gut says this has more drawbacks than i’m realizing.
I’m in search for the same white whale. There’s quite a bit of documentation for multi-seat configurations for Linux, i.e. supporting the use of multiple screens and keyboards for separate simultaneous logins.
However I’d like to remote into a separate game scope session with its own human interface inputs and virtual audio and video outputs, as the same primary user normally logged in active desktop environment session. I’d like it so the remote and local sessions would not interfere with each other state, but without necessitating multiple Linux users for each session use case.
That last bit is what makes it more tricky and very niche. Supporting essentially multiple desktop environments probably demands separate user debus sockets. Using c groups via containers makes that viable, but like you, I also like to avoid containers and extensive volume mounts.