Is it possible to run full system gui container in Incus?
Not only several apps, but full DE with desktop (gnome, kde, etc) in separate window with using host GPU and acceleration.
I searched here, but found only how to run separate GUI apps not the full system in LXC.
I know about GUI profile, but all manuals, how to run separate apps, not the whole system with separate DE in window.
Welcome!
When you run the whole desktop in a container, with hardware acceleration, the process is quite involved. You are likely going to use some stock distribution image. But those images are not designed to work inside a container. They may be looking for VTs but those are not available. And so on.
If only there was a way to find those small issues, selectively change the code, package again the fixed programs and generate new containers. That’s exactly what @tarruda did. See here, Tutorial: How to run a full desktop environment on LXD
Here is how it looks. I just took the screenshot.
Do you need to generate such desktop container images? Apparently there are such desktop container images. I am not sure how they are supposed to be used.
$ incus image list images:desktop-kde -c ldt
+------------------------------------------+--------------------------------------------+-----------------+
| ALIAS | DESCRIPTION | TYPE |
+------------------------------------------+--------------------------------------------+-----------------+
| opensuse/15.4/desktop-kde (1 more) | Opensuse 15.4 amd64 (20240515_04:20) | CONTAINER |
+------------------------------------------+--------------------------------------------+-----------------+
| opensuse/15.4/desktop-kde (1 more) | Opensuse 15.4 amd64 (20240515_04:20) | VIRTUAL-MACHINE |
+------------------------------------------+--------------------------------------------+-----------------+
| opensuse/15.5/desktop-kde (1 more) | Opensuse 15.5 amd64 (20240515_04:20) | CONTAINER |
+------------------------------------------+--------------------------------------------+-----------------+
| opensuse/15.5/desktop-kde (1 more) | Opensuse 15.5 amd64 (20240515_04:20) | VIRTUAL-MACHINE |
+------------------------------------------+--------------------------------------------+-----------------+
| opensuse/tumbleweed/desktop-kde (1 more) | Opensuse tumbleweed amd64 (20240518_05:14) | CONTAINER |
+------------------------------------------+--------------------------------------------+-----------------+
| opensuse/tumbleweed/desktop-kde (1 more) | Opensuse tumbleweed amd64 (20240518_05:14) | VIRTUAL-MACHINE |
+------------------------------------------+--------------------------------------------+-----------------+
Any remote viewers (spice or rdp protocol) have a noticable lag, poor performance and sometimes graphic quality loss 
Take a look at Parsec or HP Anywhere (formerly Teradici).
all these solutions has image compression and noticable lag.
It’s much easy run nested mutter/weston wayland instance and forward wayland socket from container. But this configuration looks weird and with a lot of edits of configuration
At some point one person will actually do this, and then the rest will copy.
Id be up to do this @Yoskaldyr , would youvlike to work together on this ?
I’d argue that running an Incus host with multiple containerised virtual desktops presented as either resizable windows or Virtual Workspaces is a very desirable capability for a rapidly growing section of the Linux user base.
Being able to run a DE version of Incus OS and fluidly switch between running Containers and Virtual Machines in precisely the same way we switch Virtual Workspaces would be an excellent user experience.
Projecting Container apps into windows on the host OS would no doubt also provide another peak user experience. Although this sounds more complex to develop.
VMware Workstation did something like this on Windows.
Wayland with Vulkan should provide a technology platform for presenting DE guests to the host, whether Containers or Virtual Machines.
Presenting a guest OS as a Virtual Workspace would be the most logical way to make guests accessible on the host — in concept and implementation.
This is what the future of the Linux DE experience and capability should hold. Conditions are ripe for it 
I’m currently running Silverblue and am thinking of establishing Incus OS as host to a primary DE guest and a mix of secondary Desktop and Server Containers, and Virtual Machines.
An ideal user experience would be an interface presented on boot to select either the host or guest in much the same way we currently select a user login.
Guests could be configured to auto start on boot or start when selected from this GUI.
This actually presents a third user experience in addition to accessing guests via windows and Virtual Workspaces — as if selecting a multi-boot option. The host OS is not loaded as is required for window and Workspace experience.
Selecting the host in the multi-boot GUI presents windows and Workspaces, selecting a guest presents just that guest, and maybe a configurable option to switch as if switching Workspaces but without exposing the host DE.
Came across Orbstack which is focused on local development with seamless host integration albeit perhaps not entirely visual like a VMware Workstation solution.
Orbstack seems to have taken a page from Incus and LXD in its adoption of system containers.
The future of the Linux DE must be seamless containerisstion 