Runtime profiles
Runtime selection determines how RelayTV reaches the display. Prefer installer detection unless the host’s intended display model is already understood.
| Profile | Choose it when | Watch for |
|---|---|---|
| Wayland | The host has a supported active Wayland session | Session socket, user, compositor, and device access |
| X11 | The host has a supported active X server | DISPLAY, X authorization, user permissions, overlays |
| DRM/KMS | RelayTV should own a compatible display device directly | Competing compositor, DRM device permissions, hardware support |
| Headless | Testing/special automation needs no physical display | Required virtual-display components may not exist in a standard image |
Verify after a profile change
Section titled “Verify after a profile change”- Run
docker compose config --quiet. - Redeploy RelayTV.
- Confirm service health.
- Start real video on the physical display.
- Check audio, seek, queue advancement, and any HDMI-CEC behavior.
- Keep the prior working override until the new profile passes.
Do not copy a generated device override from another host. It can contain display sockets, authorization files, and hardware devices unique to that box.
Canonical server source: installation runtime profiles and operations test matrix. Reviewed 2026-08-29.