Quven is a self-hosted media server for films, TV shows and documentaries, with native desktop, Android, Apple and television clients rather than a browser-only interface. The container is the Server-only lane: it scans the media you mount, matches it against the metadata providers and streams it, either direct or through HLS when the client needs it. Two things differ from most containers in Community Applications, both on purpose. The server runs as UID/GID 10001 on a read-only root filesystem with every capability dropped, so the appdata directory has to belong to that user before the first start. From a terminal: mkdir -p /mnt/user/appdata/quven && chown -R 10001:10001 /mnt/user/appdata/quven The media share is mounted read-only. Quven never writes to it during a scan, and an ordinary scan is not a disk-cleaning operation. Host networking is used because the server answers LAN discovery from the native clients, on port 5181. There is no page to open in a browser here. Quven's clients are native, and app.quven.tv reaches a linked server through the managed relay rather than through this port. Once the container is up, link it to your Quven Account, which is what lets a client sign in: docker exec -it Quven /app/Quven.Local.Server account link Open the URL it prints, approve the server, and the clients on your network will find it. Hardware transcoding is not offered here. The server runs unprivileged, so a render node alone is not enough: it also needs the host's render and video group IDs, which are specific to your machine and which this template cannot guess. Use the Docker Compose bundle on quven.tv for a VA-API, NVIDIA or Raspberry Pi setup.