Skip to content

Commit 7c76a02

Browse files
Bot Updating Templated Files
1 parent 0ddb06a commit 7c76a02

1 file changed

Lines changed: 18 additions & 14 deletions

File tree

README.md

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -89,20 +89,28 @@ The web interface includes a terminal with passwordless `sudo` access. Any user
8989

9090
While not generally recommended, certain legacy environments specifically those with older hardware or outdated Linux distributions may require the deactivation of the standard seccomp profile to get containerized desktop software to run. This can be achieved by utilizing the `--security-opt seccomp=unconfined` parameter. It is critical to use this option only when absolutely necessary as it disables a key security layer of Docker, elevating the potential for container escape vulnerabilities.
9191

92-
### Hardware Acceleration & The Move to Wayland
92+
### FullColor 4:4:4 Encoding
9393

94-
We are currently transitioning our desktop containers from X11 to Wayland. While X11 is still the default, we strongly encourage users to test the new Wayland mode.
94+
If you notice blurry text, particularly light text on a black background, you can send true 8-bit color to the browser by enabling the **FullColor 4:4:4** encoding in the sidebar, or by using the jpeg encoding mode.
9595

96-
**Important:** GPU acceleration support for X11 is being deprecated. Future development for hardware acceleration will focus entirely on the Wayland stack.
96+
**Note on Hardware Acceleration:** Currently, only Nvidia GPUs support encoding this color profile in **Zero Copy** mode. If FullColor 4:4:4 is enabled on Intel or AMD GPUs, the system will fall back to CPU encoding. This forces the CPU to read the pixels back from the GPU, which will cause a significant decrease in performance.
9797

98-
To enable Wayland mode, set the following environment variable:
98+
### Hardware Acceleration & Wayland
9999

100-
* `-e PIXELFLUX_WAYLAND=true`
100+
We have transitioned our desktop containers from X11 to a modern Wayland stack, which is now the default.
101101

102-
**Why use Wayland?**
102+
**Hardware Fallback Note:** On `x86_64` architecture, the Wayland stack requires a processor with AVX2 support (Intel Haswell generation or newer). If your processor lacks AVX2 (such as older CPUs or certain low-end Celerons), the container will automatically fall back to X11.
103+
104+
**Important:** GPU acceleration support for X11 is deprecated. Future development for hardware acceleration is focused entirely on the Wayland stack.
105+
106+
If you experience compatibility issues and need to manually disable Wayland (forcing a fallback to X11), you can do so by setting the following environment variable:
107+
108+
* `-e PIXELFLUX_WAYLAND=false`
109+
110+
**Why Wayland?**
103111

104112
* **Zero Copy Encoding:** When configured correctly with a GPU, the frame is rendered and encoded on the video card without ever being copied to the system RAM. This drastically lowers CPU usage and latency.
105-
* **Modern Stack:** Single-application containers utilize **Labwc** (replacing Openbox) and full desktop containers use **KDE Plasma Wayland**, providing a more modern and secure compositing environment while retaining the same user experience.
113+
* **Modern Stack:** Single-application containers utilize **Labwc** (replacing Openbox) and full desktop containers use **KDE Plasma Wayland**, providing a more modern, performant, and secure compositing environment while retaining the same user experience.
106114

107115
#### GPU Configuration
108116

@@ -133,12 +141,8 @@ For Intel and AMD GPUs.
133141
134142
##### Nvidia (Proprietary Drivers)
135143
136-
**Note: Nvidia support is currently considered experimental, driver changes can break it at any time.**
137-
138144
**Note: Nvidia support is not available for Alpine-based images.**
139145
140-
**Note: Nvidia frames have issues with hardware decoders in Chromium browsers you need to navigate to `chrome://flags/#disable-accelerated-video-decode` and toggle it to `Disabled` for smooth playback**
141-
142146
**Prerequisites:**
143147
144148
1. **Driver:** Proprietary drivers **580 or higher** are required. **Crucially, you should install the driver using the `.run` file downloaded directly from the Nvidia website.**
@@ -210,7 +214,7 @@ This container is based on [Docker Baseimage Selkies](https://github.com/linuxse
210214

211215
| Variable | Description |
212216
| :----: | --- |
213-
| PIXELFLUX_WAYLAND | **Experimental** If set to true the container will initialize in Wayland mode running [Smithay](https://github.com/Smithay/smithay) and Labwc while enabling zero copy encoding with a GPU |
217+
| PIXELFLUX_WAYLAND | If set to true the container will initialize in Wayland mode running [Smithay](https://github.com/Smithay/smithay) and Labwc while enabling zero copy encoding with a GPU |
214218
| SELKIES_DESKTOP | If set to true and in Wayland mode, a simple panel will be initialized with labwc |
215219
| CUSTOM_PORT | Internal port the container listens on for http if it needs to be swapped from the default `3000` |
216220
| CUSTOM_HTTPS_PORT | Internal port the container listens on for https if it needs to be swapped from the default `3001` |
@@ -265,14 +269,14 @@ This container is based on [Docker Baseimage Selkies](https://github.com/linuxse
265269

266270
When using 3d acceleration via Nvidia DRM or DRI3 in X11 mode, it is important to clamp the virtual display to a reasonable max resolution to avoid memory exhaustion or poor performance.
267271

268-
* `-e MAX_RESOLUTION=3840x2160`
272+
* `-e MAX_RES=3840x2160`
269273

270274
This will set the total virtual framebuffer to 4K. By default, the virtual monitor is 16K. If you have performance issues in an accelerated X11 session, try clamping the resolution to 1080p and work up from there:
271275

272276
```bash
273277
-e SELKIES_MANUAL_WIDTH=1920
274278
-e SELKIES_MANUAL_HEIGHT=1080
275-
-e MAX_RESOLUTION=1920x1080
279+
-e MAX_RES=1920x1080
276280
```
277281

278282
</details>

0 commit comments

Comments
 (0)