</span></code></pre></div><p>And we can define the application to start using: </p><divclass="language-text highlight"><pre><span></span><code><spanid=__span-1-1><aid=__codelineno-1-1name=__codelineno-1-1href=#__codelineno-1-1></a>mkdir -p root/defaults
</span></code></pre></div><p>Resulting in a folder that looks like this: </p><divclass="language-text highlight"><pre><span></span><code><spanid=__span-2-1><aid=__codelineno-2-1name=__codelineno-2-1href=#__codelineno-2-1></a>├── Dockerfile
</span></code></pre></div><p>Now build and test:</p><divclass="language-text highlight"><pre><span></span><code><spanid=__span-3-1><aid=__codelineno-3-1name=__codelineno-3-1href=#__codelineno-3-1></a>docker build -t firefox .
</span><spanid=__span-3-2><aid=__codelineno-3-2name=__codelineno-3-2href=#__codelineno-3-2></a>docker run --rm -it -p 3000:3000 firefox bash
</span></code></pre></div><p>On http://localhost:3000 you should be presented with a Firefox web browser interface.</p><p>This similar setup can be used to embed any Linux Desktop application in a web accesible container.</p><p><strong>If building images it is important to note that many application will not work inside of Docker without <code>--security-opt seccomp=unconfined</code>, they may have launch flags to not use syscalls blocked by Docker like with chromium based applications and <code>--no-sandbox</code>. In general do not expect every application will simply work like a native Linux installation without some modifications</strong></p><h4id=in-container-application-launching>In container application launching<aclass=headerlinkhref=#in-container-application-launchingtitle="Permanent link">¶</a></h4><p>Also included in the init logic is the ability to define application launchers. As the user has the ability to close the application or if they want to open multiple instances of it this can be useful. Here is an example of a menu definition file for Firefox:</p><divclass="language-text highlight"><pre><span></span><code><spanid=__span-4-1><aid=__codelineno-4-1name=__codelineno-4-1href=#__codelineno-4-1></a><?xml version="1.0" encoding="utf-8"?>
</span></code></pre></div><p>Simply create this file and add it to your defaults folder as <code>menu.xml</code>: </p><divclass="language-text highlight"><pre><span></span><code><spanid=__span-5-1><aid=__codelineno-5-1name=__codelineno-5-1href=#__codelineno-5-1></a>├── Dockerfile
</span></code></pre></div><p>This allows users to right click the desktop background to launch the application.</p><h3id=full-desktop-environments>Full Desktop environments<aclass=headerlinkhref=#full-desktop-environmentstitle="Permanent link">¶</a></h3><p>When building an application container we are leveraging the Openbox DE to handle window management, but it is also possible to completely replace the DE that is launched on container init using the <code>startwm.sh</code> script, located again in defaults: </p><divclass="language-text highlight"><pre><span></span><code><spanid=__span-6-1><aid=__codelineno-6-1name=__codelineno-6-1href=#__codelineno-6-1></a>├── Dockerfile
</span></code></pre></div><p>If included in the build logic it will be launched in place of Openbox. Examples for this kind of configuration can be found in our <ahref=https://github.com/linuxserver/docker-webtop>Webtop repository</a></p><h3id=kasm-workspaces-compatibility>Kasm Workspaces compatibility<aclass=headerlinkhref=#kasm-workspaces-compatibilitytitle="Permanent link">¶</a></h3><p>Included in these base images are binary blobs <code>/kasmbins</code> and a special init process <code>/kasminit</code> to maintain compatibility with <ahref=https://www.kasmweb.com/>Kasm Workspaces</a>, If using this base image as reccomended with the <code>startwm.sh</code> or <code>autostart</code> entrypoints. They will be able to be used on that platform without issue.</p><h2id=docker-in-docker-dind>Docker in Docker (DinD)<aclass=headerlinkhref=#docker-in-docker-dindtitle="Permanent link">¶</a></h2><p>These base images include an installation of Docker that can be used in two ways. The simple method is simply leveraging the Docker/Docker Compose cli bins to manage the host level Docker installation by mounting in <code>-v /var/run/docker.sock:/var/run/docker.sock</code>. </p><p>The base images can also run an isolated in container DinD setup simply by passing <code>--privileged</code> to the container when launching. If for any reason the application needs privilege but Docker is not wanted the <code>-e START_DOCKER=false</code> can be set at runtime or in the Dockerfile. In container Docker (DinD) will most likely use the fuse-overlayfs driver for storage which is not as fast as native overlay2. To increase perormance the <code>/var/lib/docker/</code> directory in the container can be mounted out to a Linux host and will use overlay2. Keep in mind Docker runs as root and the contents of this directory will not respect the PUID/PGID environment variables available on all LinuxServer.io containers.</p><h2id=dri3-gpu-acceleration>DRI3 GPU Acceleration<aclass=headerlinkhref=#dri3-gpu-accelerationtitle="Permanent link">¶</a></h2><p>For accelerated apps or games, render devices can be mounted into the container and leveraged by applications using: </p><p><code>--device /dev/dri:/dev/dri</code></p><p>This feature only supports <strong>Open Source</strong> GPU drivers:</p><table><thead><tr><thstyle="text-align: center;">Driver</th><th>Description</th></tr></thead><tbody><tr><tdstyle="text-align: center;">Intel</td><td>i965 and i915 drivers for Intel iGPU chipsets</td></tr><tr><tdstyle="text-align: center;">AMD</td><td>AMDGPU, Radeon, and ATI drivers for AMD dedicated or APU chipsets</td></tr><tr><tdstyle="text-align: center;">NVIDIA</td><td>nouveau2 drivers only, closed source NVIDIA drivers lack DRI3 support</td></tr></tbody></table><p>The <code>DRINODE</code> environment variable can be used to point to a specific GPU. Up to date information can be found <ahref=https://www.kasmweb.com/kasmvnc/docs/master/gpu_acceleration.html>here</a></p><h2id=lossless>Lossless<aclass=headerlinkhref=#losslesstitle="Permanent link">¶</a></h2><p>These images support all the native KasmVNC encoding methods including a true 24 bit RGB lossless mode using the <ahref=https://qoiformat.org/>Quite OK Image Format</a>. This mode will use all the bandwidth you give it so just keep that in mind for remote sessions. This mode also might require special configuration depending on how you are accessing the container. Lossless will only work over http (default port 3000) on localhost, when accessing remotely or even over a local network you need to use https (default port 3001) to support <ahref=https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer>SharedArrayBuffer</a>. This is needed to leverage a fast memory pipeline in the browser during the threaded WebAssembly based decoding. This can be enabled in the sidebar under settings>stream quality>lossless.</p><p>If putting this container behind a proxy of some kind some headers will nee
