Appearance
Media Server Host Setup
The media server runs Ubuntu directly on its hardware. Docker hosts Jellyfin, the media-management applications, and Kopia. The Intel integrated GPU handles Jellyfin transcoding, while NAS shares hold media and application backups.
For AI provisioning, SSH access, credentials, and recovery procedures, see Media Server · Internal Operations.
Configuration
| Setting | This homelab | For another installation |
|---|---|---|
| OS | Ubuntu Server 24.04 LTS | A supported Ubuntu Server release |
| Hostname | media-server | Your chosen server name |
| Address | 10.120.40.105/24 | A reserved address on your server network |
| Gateway | 10.120.40.1 | Your router |
| Bootstrap DNS | 1.1.1.1 | A reachable resolver |
| Media share | //10.120.40.6/Media | Your NAS media share |
| Backup share | //10.120.40.6/Server_Backups | Your NAS backup share |
| Local projects | /docker/jellyfin, /docker/servarr, /docker/kopia | Local directories for application state |
Use the lab values to reproduce this host, or replace addresses, shares, account names, and paths consistently for another homelab. See Servers for hardware and Media Server services for application roles and access.
Install Ubuntu
Download and verify the Ubuntu Server installer, write it to USB, and boot the physical server. Keep a keyboard and monitor available for recovery.
Choose the internal SSD for Ubuntu and local application state. Installation can erase the selected disk, so verify its model and back up existing data first. Leave the media library on the NAS. Create a normal administrator account with sudo access and enable OpenSSH Server. Install Docker later from its official repository rather than through an installer snap.
For manual network configuration, use subnet 10.120.40.0/24, address 10.120.40.105, gateway 10.120.40.1, and the bootstrap resolver above. The subnet field takes the network address, not the host address. Reserve or exclude the server address in DHCP so it cannot be assigned elsewhere.
After reboot:
sh
hostnamectl
ip -brief address
ip route
sudo apt update
sudo apt upgrade
sudo apt install ca-certificates cifs-utils curl pciutils rsyncSet up key-only SSH
Install your selected public key for the administrator account without replacing existing keys. Prove a fresh key-authenticated session before disabling password and keyboard-interactive authentication. Validate changes with sudo sshd -t, inspect the effective policy with sudo sshd -T, and reload ssh.service while keeping the working session open. Verify another key login and rejection of password authentication before closing the bootstrap connection.
For a new Ubuntu host, create an early SSH drop-in such as /etc/ssh/sshd_config.d/00-key-only.conf after key login works:
text
PubkeyAuthentication yes
PasswordAuthentication no
KbdInteractiveAuthentication no
PermitRootLogin noUse sudo sshd -T to confirm these values take effect; earlier settings and connection-specific Match rules can affect the result. This example assumes a working non-root sudo account. Do not apply its root-login restriction to a host whose only SSH administrator is the superuser, such as this lab's Proxmox host.
The lab's exact account and reviewed configuration assets are in the internal runbook. Keep the physical console available throughout this change.
Verify the Intel GPU
sh
lspci -knn
ls -l /dev/dri
test -c /dev/dri/renderD128This host uses Intel Meteor Lake integrated graphics with the i915 driver and render device /dev/dri/renderD128. On another machine, use the driver and render node actually detected. If the device is absent, check firmware settings, updates, and kernel messages before configuring Jellyfin.
Jellyfin receives /dev/dri directly from Ubuntu. There is no hypervisor or LXC GPU passthrough layer on this host.
Mount NAS storage
NAS storage is optional
This homelab stores media on a NAS, but you can keep media on local storage instead. If you are not using a NAS, skip this section and the NAS mount dependency steps under Docker setup. Use your local media paths in the application configurations. If you also keep backups locally, update Kopia's repository path accordingly and maintain a separate off-host recovery copy.
Create protected credentials
Create the mount directories and a root-only credential location:
sh
sudo mkdir -p /mnt/unaspro/media /mnt/unaspro/server-backups
sudo install -d -m 0700 /etc/samba/credentials
sudoedit /etc/samba/credentials/media-serverEnter your NAS account in the file using this format, replacing placeholders locally:
ini
username=<nas-user>
password=<nas-password>sh
sudo chown root:root /etc/samba/credentials/media-server
sudo chmod 600 /etc/samba/credentials/media-server
idKeep the original credentials in your password manager. Use the administrator account's actual numeric UID and primary GID in the mount options below; 1000:1000 is only an example.
Configure persistent mounts
Edit /etc/fstab and add the following, adapting the NAS address, shares, credential path, UID, and GID:
text
//10.120.40.6/Media /mnt/unaspro/media cifs credentials=/etc/samba/credentials/media-server,iocharset=utf8,uid=1000,gid=1000,file_mode=0664,dir_mode=0775,_netdev,nofail,x-systemd.mount-timeout=30s 0 0
//10.120.40.6/Server_Backups /mnt/unaspro/server-backups cifs credentials=/etc/samba/credentials/media-server,vers=3.1.1,iocharset=utf8,uid=1000,gid=1000,file_mode=0600,dir_mode=0700,_netdev,nofail,x-systemd.mount-timeout=30s 0 0The credential filename here is a generic example; preserve an existing working credential path on the lab host. nofail lets Ubuntu remain accessible when the NAS is unavailable. Docker will separately require the mounts so containers cannot start against empty local directories.
sh
sudo systemctl daemon-reload
sudo mount /mnt/unaspro/media
sudo mount /mnt/unaspro/server-backups
findmnt /mnt/unaspro/media
findmnt /mnt/unaspro/server-backups
test -r /mnt/unaspro/media && test -w /mnt/unaspro/media
test -r /mnt/unaspro/server-backups && test -w /mnt/unaspro/server-backups
mkdir -p /mnt/unaspro/server-backups/media-server
chmod 700 /mnt/unaspro/server-backups/media-serverBoth mounts must report the intended NAS source and CIFS filesystem. An existing local directory alone does not prove a share is mounted. See Ubuntu's permanent CIFS mount guide for additional options.
Install Docker Engine
Configure Docker's signed APT repository for your Ubuntu release. On a fresh Ubuntu host:
sh
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
sudo tee /etc/apt/sources.list.d/docker.sources >/dev/null <<EOF
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOFIf Docker is already installed, inspect the current packages and repository first; follow the official installation guide to resolve conflicting packages instead of adding a second installation. Install the engine and Compose plugin:
sh
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginAdd your chosen administrator to the Docker group if you want to manage Docker without sudo, then start a fresh login. Docker-group membership grants root-equivalent control of the host. Use sudo docker until that account is configured.
sh
docker compose version
docker run --rm hello-worldRequire real NAS mounts before Docker starts
Before deploying application containers, create /etc/systemd/system/docker.service.d/media-mount.conf:
sh
sudo mkdir -p /etc/systemd/system/docker.service.d
sudoedit /etc/systemd/system/docker.service.d/media-mount.confini
[Unit]
Wants=network-online.target
Requires=mnt-unaspro-media.mount mnt-unaspro-server\x2dbackups.mount
After=network-online.target mnt-unaspro-media.mount mnt-unaspro-server\x2dbackups.mountFor different mount paths, obtain their unit names with systemd-escape --path --suffix=mount /your/mount/path and replace both references. The literal \x2d sequence is systemd's escaped hyphen in the backup mount's unit name.
sh
sudo systemctl daemon-reload
sudo systemctl restart docker
systemctl show docker.service --property=Requires --property=AfterThis restart interrupts any containers already running. Set up the dependency before the initial application deployment. It gates Docker startup; it does not continuously monitor SMB availability after startup.
Bound container logs
Merge this configuration into /etc/docker/daemon.json, preserving any existing settings:
json
{
"log-driver": "json-file",
"log-opts": {
"compress": "true",
"max-file": "5",
"max-size": "10m"
}
}Validate with sudo dockerd --validate --config-file=/etc/docker/daemon.json, then restart Docker during maintenance. Log defaults apply when containers are created; existing containers need recreation to inherit them. Keep Docker live restore disabled for the lab's coordinated power-shutdown design.
Prepare application directories and port bindings
Create the directories and assign ownership to your deployment account. For a fresh host, run these commands as that account:
sh
sudo mkdir -p /docker/jellyfin /docker/servarr /docker/kopia
sudo chown "$(id -u):$(id -g)" /docker /docker/jellyfin /docker/servarr /docker/kopiaSet SERVER_IP=10.120.40.105 in /etc/environment, preserving other entries. Start a new login and verify printenv SERVER_IP. The media stack definitions use this value for published-port bindings; scheduled backup services also need to load /etc/environment.
The normal web entry point is Nginx Proxy Manager. Bindings to the host IP also allow direct backend access from networks permitted by the router. Changing SERVER_IP does not change the host's network configuration, proxy destinations, or firewall rules automatically.
Verify startup and storage recovery
After initial host setup, perform a controlled reboot before depending on unattended startup. Confirm:
sh
findmnt /mnt/unaspro/media
findmnt /mnt/unaspro/server-backups
systemctl is-active docker
free -h
df -hIf the NAS was unavailable at boot, restore NAS access, mount and verify both shares, then start Docker. Do not bypass the mount dependency to make containers start. The lab also has UPS and NAS-readiness integration; restore it using the internal runbook before relying on automatic outage recovery.
Configure services and backups
Continue with Streaming and requests, Library and subtitles, Downloads and indexers, and Backups.
Keep application databases on local Linux storage and media on the mounted NAS. Kopia protects application state, not the media library or a full operating-system image. Keep a protected rebuild record of mount, Docker, SSH, audit, and systemd configuration plus recovery copies of secrets. The media library requires its own NAS backup policy.
Before replacing the system disk, verify an external backup of host configuration and application state. Ubuntu detects added RAM automatically; check free -h after installation. Deployment scripts, environment templates, audit rules, and service units remain in the private homelab repository. The internal runbook explains how to apply those exact assets.