Docker Usenet stack
Short answer
A working Docker setup for Usenet is SABnzbd, Prowlarr, Sonarr and Radarr in one compose file, with the same data folder and the same PUID and PGID. Inside SABnzbd, add Newshosting (news.newshosting.com, port 563, SSL) at priority 0, and an optional backup server on another backbone, such as a NewsgroupDirect block, at priority 1.
Running Usenet in Docker comes down to three things. Put SABnzbd (or NZBGet), Prowlarr, Sonarr and Radarr in one compose file, give them a single shared /data mount, and run every container as the same user. The provider side is no different from a normal install: you enter the provider hostname, port 563 and your login in the downloader once, and Docker never touches them. On a NAS, start with Usenet on Synology, which has a Container Manager version with Synology paths.
The quick path
- Create the folders. TRaSH Guides publishes this command for Usenet:
mkdir -p /data/{usenet/{incomplete,complete}/{tv,movies,music},media/{tv,movies,music}}. Change/dataat the start to your own folder. For the file below, that is/srv/data. - Run
id youruserand put the uid and gid in the compose file below as PUID and PGID. - Save the file as
docker-compose.ymland rundocker compose up -d. - Set up SABnzbd at
http://your-host:8080with the SABnzbd setup guide, and point its folders to/data/usenet/incompleteand/data/usenet/complete. - Add your indexers in Prowlarr at port 9696, using their API keys, and connect Sonarr at 8989 and Radarr at 7878.
A working docker-compose example
Image names and ports come from the linuxserver docs, and the tags were current on 7 Nov 2026. These builds change within days, so check for newer ones before you start. We changed the volumes to the layout from TRaSH Guides: SABnzbd sees /data/usenet, and Sonarr and Radarr see all of /data, so files can be moved instead of copied. The maintainers' own default of separate /downloads paths loses that, according to their READMEs. The full picture of what this does is in the automation stack guide.
services:
sabnzbd:
image: lscr.io/linuxserver/sabnzbd:5.1.3-ls280
container_name: sabnzbd
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Amsterdam
volumes:
- /srv/appdata/sabnzbd:/config
- /srv/data/usenet:/data/usenet
ports:
- 8080:8080
restart: unless-stopped
prowlarr:
image: lscr.io/linuxserver/prowlarr:2.7.0.5723-ls167
container_name: prowlarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Amsterdam
volumes:
- /srv/appdata/prowlarr:/config
ports:
- 9696:9696
restart: unless-stopped
sonarr:
image: lscr.io/linuxserver/sonarr:4.0.20.3014-ls3
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Amsterdam
volumes:
- /srv/appdata/sonarr:/config
- /srv/data:/data
ports:
- 8989:8989
restart: unless-stopped
radarr:
image: lscr.io/linuxserver/radarr:6.4.4.10685-ls325
container_name: radarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Amsterdam
volumes:
- /srv/appdata/radarr:/config
- /srv/data:/data
ports:
- 7878:7878
restart: unless-stopped
The containers and what each one does
- SABnzbd: connects to your provider over NNTP, repairs downloads with par2, unpacks RAR files and moves the result into a category folder.
- Prowlarr: keeps your indexer API keys and passes them on to the other apps.
- Sonarr and Radarr: search indexers, send NZBs to SABnzbd and import finished files into your library.
- Optional: Lidarr for music and Bazarr for subtitles. Lidarr relies on older posts more than TV does, so your provider matters more there; see Usenet for Lidarr. Bazarr never downloads from Usenet and has no bearing on which provider you pick, as Usenet for Bazarr explains.
One /data tree, one user
Most failed imports in Docker come down to paths. Use a single host folder, for example /srv/data, with usenet/incomplete, usenet/complete and media inside it. Sonarr and Radarr mount it as /data, and SABnzbd mounts the usenet part at /data/usenet. Sonarr then finds /data/usenet/complete/tv at exactly the path SABnzbd reported, and can move the file rather than copy it.
The LinuxServer and hotio images read PUID and PGID. Give them the same values in every service, and chown the host folder to that user once. If SABnzbd writes as one user and Sonarr reads as another, the Sonarr log fills with permission denied errors, which have nothing to do with retention or your provider.
Networking between containers
On a shared compose network, Sonarr reaches the downloader at http://sabnzbd:8080. Use that name in the download client settings rather than the host IP. Only expose the SABnzbd web port on your own network or behind a reverse proxy with a login. Copy the SABnzbd API key into Sonarr and Radarr, and keep it out of screenshots.
If SABnzbd runs through a VPN container such as Gluetun, test two things after every change: that the container can still resolve the provider hostname, and that a manual NZB still finishes at your usual speed. A broken DNS setting inside the VPN container makes every job fail as soon as it tries to connect.
Example: the server settings inside SABnzbd
This is a common two-provider setup. Hosts and connection limits were checked on the providers' own help pages on 7 Nov 2026. The main account is Newshosting on Highwinds. The backup server, often called a fill server, is a NewsgroupDirect block on UsenetExpress, a different backbone that can supply articles Newshosting has lost.
| Setting | Server 1 (main account) | Server 2 (backup) |
|---|---|---|
| Host | news.newshosting.com | news.newsgroupdirect.com |
| Port and SSL | 563, SSL on | 563, SSL on |
| Backbone | Highwinds (DMCA) | UsenetExpress (DMCA) |
| Plan maximum connections | 100 | Not stated for blocks (100 on its subscriptions) |
| Priority | 0 | 1 |
| Optional | off | on |
| Price | $12.95/mo on 12 months | 500 GB for $25, checked 22 Oct 2026 |
Keep connections under the plan maximum. On a small NAS, a container runs out of CPU for SSL and par2 long before it reaches 100 connections. Do not use UsenetServer or Easynews as server 2, because they read from the same Highwinds servers as Newshosting and are missing the same articles.
Updates and backups
Pin image tags rather than using latest, and read the release notes before you update. Do keep updating, though: SABnzbd 5.1.1 to 5.1.3 fix critical security holes, so don't sit on an older tag. Back up each app's /config folder on its own schedule. The Sonarr and Radarr databases hold your series, quality profiles and path mappings, none of which you can rebuild from the media files. The SABnzbd config contains your provider passwords, so keep that backup private. For the downloader's own setup screens, see the SABnzbd setup guide.
FAQ
- SABnzbd or NZBGet in Docker?
- SABnzbd has more examples and templates for the arr apps. NZBGet uses less memory, which is useful on small ARM boards.
- Why did imports break after I moved to Docker?
- Either the downloader and Sonarr see different paths, or they run as different users. Give both the same /data mount and the same PUID and PGID.
- Does Docker change how many downloads complete?
- No. That depends on your provider's backbone and retention. Docker only changes how the software is packaged.