Run SABnzbd, NZBHydra2, and Sonarr with systemd user services and Docker or Podman. The packages target Arch Linux.
- Podman setup and usage: install
sabnzbd-podmanand configure~/.podman-sabnzbd.env. - Docker setup and usage: install
sabnzbd-dockerand configure~/.docker-sabnzbd.env.
Install only one variant. Both use the same container names and default ports. The Docker package also declares a conflict with the Podman package.
The sabnzbd-docker AUR entry provides another installation option.
The Compose file uses these LinuxServer.io images:
| Application | Image | Default address |
|---|---|---|
| SABnzbd | lscr.io/linuxserver/sabnzbd:latest |
http://localhost:8080 |
| NZBHydra2 | lscr.io/linuxserver/nzbhydra2:latest |
http://localhost:5076 |
| Sonarr | lscr.io/linuxserver/sonarr:latest |
http://localhost:8989 |
Ports bind to all host interfaces by default. Restrict access with application settings and your firewall.
- Use persistent, absolute host paths. The packaged
/tmpdata defaults are not suitable for persistent storage. - Create the host directories before starting containers.
- Configure application paths using container paths, such as
/downloads, rather than host paths. - Keep assignments in
NAME=valueform, without spaces around=. - Put comments on separate lines. Systemd environment files do not support shell-style inline comments.
- Use literal absolute paths in user configuration files. Do not rely on
$HOMEor~expansion. - Use
COMPOSE_PROFILES=allfor all applications, or select profiles such assabnzbd,nzbhydra2.
Run service-management commands on the host, not inside a restricted development sandbox.