Requirements and hardware
Required
Section titled “Required”- A 64-bit
amd64orarm64Linux host - A display connected to that host
- A supported display runtime for the intended deployment
- Docker Engine and Compose v2, or approval for the installer to add them
- Network access from the devices that will control RelayTV
Mini PCs, NUCs, HTPCs, and capable Raspberry Pi-class devices are common fits. The processor architecture alone does not guarantee codec, resolution, HDR, audio, or HDMI-CEC behavior.
Display runtime
Section titled “Display runtime”RelayTV supports several runtime profiles with different prerequisites:
| Profile | Typical use | Important prerequisite |
|---|---|---|
| Wayland | Modern desktop session | An active graphical session available to the container/runtime |
| X11 | Traditional desktop session | Display and authorization access for the RelayTV process |
| DRM/KMS | Direct display ownership | Compatible DRM devices and no competing desktop compositor |
| Headless | Testing or special workflows | A build/runtime that includes the required virtual display support |
Do not select headless merely because the host has no keyboard. A living-room
host rendering to a TV is not headless.
Optional hardware
Section titled “Optional hardware”/dev/drifor compatible GPU acceleration/dev/cec*for HDMI-CEC control when the host and adapter expose it- a specific audio sink when automatic selection is not correct
Network
Section titled “Network”RelayTV is designed for a trusted LAN. Controllers need to reach the server on
port 8787; automatic discovery also requires working mDNS on the local network.
Across untrusted networks, use a VPN or authenticated reverse proxy and enable the optional RelayTV bearer token. See Security and network.
Canonical server source: installation guide and runtime test matrix. Reviewed 2026-08-29.