The LinuxServer.io team brings you another container release featuring easy user mapping and community support. Find us for support at:
- IRC on freenode at
- Podcast covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!
SABnzbd makes Usenet as simple and streamlined as possible by automating everything we can. All you have to do is add an .nzb. SABnzbd takes over from there, where it will be automatically downloaded, verified, repaired, extracted and filed away with zero human interaction.
docker create --name=sabnzbd \ -v <path to data>:/config \ -v <path to downloads>:/downloads \ -v <path to incomplete downloads>:/incomplete-downloads \ -e PGID=<gid> -e PUID=<uid> \ -e TZ=<timezone> \ -p 8080:8080 -p 9090:9090 \ linuxserver/sabnzbd
You can choose ,using a tag, to use the unstable branch.
Stable is the default and requires no tag
(at times both branches may have the same version, but the stable/latest branch should never contain an alpha/beta/rc version)
Add the tag, if required, to the linuxserver/sabnzbd line of the run/create command in the following format:-
The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.
For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container.
So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080
http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.
-p 8080- http port for the webui
-p 9090- https port for the webui see note below
-v /config- local path for sabnzbd config files
-v /downloadslocal path for finished downloads
-v /incomplete-downloadslocal path for incomplete-downloads - optional
-e PGIDfor GroupID - see below for explanation
-e PUIDfor UserID - see below for explanation
-e TZfor setting timezone information, eg Europe/London
It is based on ubuntu xenial with s6 overlay, for shell access whilst the container is running do
docker exec -it sabnzbd /bin/bash.
User / Group Identifiers
Sometimes when using data volumes (
-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user
PUID and group
PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
In this instance
PGID=1001. To find yours use
id user as below:
$ id <dockeruser> uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
Setting up the application
Initial setup is done from the http port.
Https access for sabnzbd needs to be enabled in either the intial setup wizard or in the configure settings of the webui, be sure to use 9090 as port for https.
See here for info on some of the switch settings for sabnzbd http://wiki.sabnzbd.org/configure-switches
- Shell access whilst the container is running:
docker exec -it sabnzbd /bin/bash
- To monitor the logs of the container in realtime:
docker logs -f sabnzbd
- 10.04.17: Bump to 2.0 Release.
- 25.02.17: Switch to nobetas repo for master/latest branch and add unstable branch.
- 08.02.17: Add pythonioenconding=utf8 as env.
- 15.09.16: Compile par2 multicore as per latest info sabnzbd git readme
- 11.09.16: Bump to release of 1.10
- 09.09.16: Rebase back to xenial,
issues with alpine version of python and 1.10 branch of sab.
- 28.08.16: Rebase to alpine, using git version of sab.
- 17.03.16: Bump to install 1.0 final at startup
- 14.03.16: Refresh image to pick up latest RC
- 23.01.15: Refresh image.
- 14.12.15: Refresh image to pick up latest beta
- 21.08.15: Intial Release.
There seems tobe a minor problem with running this on docker for windows. After a shutdown or restart there is a high chance that the /Admin/*.sab (rss_data/totals) files get corrupted and saved with a file size of 0. So after the restart sabnzbd complains about this via a error entry in the interface.
Would be great if you could also include the watch directory of Sabnzbd for mapping. Thanks!
Thanks for the awesome image, I have one little problem, which I googled but probably not good enough:
API key incorrect, Use the API key from Config->General in your 3rd party program: 10.0.3.1>python-requests/2.12.3
Seems like the docker image is pinging itself (May be wrong). What did I do wrong/ Can I do? Thanks a lot.