From 6111ec8ce3ffc6824e84d5c2b5589d9ef2c53fd5 Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Sun, 1 Mar 2026 17:04:13 +0000 Subject: [PATCH] Bot Updating Documentation --- docs/images/docker-sealskin.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/images/docker-sealskin.md b/docs/images/docker-sealskin.md index 5082bc5c5f..f97515e07e 100644 --- a/docs/images/docker-sealskin.md +++ b/docs/images/docker-sealskin.md @@ -67,6 +67,8 @@ This will setup pathing, ownership, docker config, and a legit wildcard SSL cert It is important to use the container name `sealskin` as this is how the container identifies itself and determines its ports, volumes, and network. The only backend provider to launch containers is Docker. The storage paths are required for key and storage management while their mount paths are adapted from within the container to be run on the host for launched sessions. Everyting in the stack runs as the PUID and PGID down to the container desktop sessions, it is important that the user you use has access to the `/config` and `/storage` paths. +The entire stack is not designed to run behind a reverse proxy, but it is meant to be directly exposed to the internet. + ### NVIDIA Support Nvidia support only works on 580 and up full proprietary drivers (no MIT/GPL) with `nvidia-drm.modeset=1` kernel parameter set. You must ensure the card is initialized before running a container so on headless systems run `nvidia-modprobe --modeset` from the host even with this kernel parameter set, this only needs to be run once per boot on headless systems.