The media stack serves a personal library built mostly from owned DVDs and Blu-rays. Jellyfin is the main user-facing piece, with supporting containers for metadata, organization, and maintenance.
Architecture
The stack is split between compute and storage. Media files live on the NAS, while the media LXC handles the containers and hardware-encoding side of the workload. The storage is mounted into the media environment through a network share and bind mount pattern.
This split keeps large storage on the NAS while letting Proxmox handle the compute and passthrough needs.
Services
Jellyfin is the service that actually gets used day to day. Radarr and Sonarr help with metadata and library organization.
The media LXC is also where camera/object-detection workloads can live, because those workloads have similar hardware-encoding requirements.
Tradeoffs
The LXC and service configs are backed up through the Proxmox backup path. The media library itself is large and lower priority than photos, personal files, and system backups, so it is not treated as a top off-site backup target right now.
The main lesson is that a media stack is a surprisingly useful architecture exercise. It touches containers, NAS storage, network mounts, GPU/passthrough, client compatibility, remote access, update routines, and the rough edges of open-source user experience.
It is also a good reminder that not every large dataset deserves the same backup treatment. The service configuration and playback environment matter more than treating a massive, replaceable media library like irreplaceable personal data.