linuxserver/sabnzbd
A Sabnzbd container, brought to you by LinuxServer.io.
500M+
The LinuxServer.io team brings you another container release featuring:
Find us at:
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.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/sabnzbd:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture | Available | Tag |
---|---|---|
x86-64 | ✅ | amd64-<version tag> |
arm64 | ✅ | arm64v8-<version tag> |
armhf | ❌ |
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
Tag | Available | Description |
---|---|---|
latest | ✅ | Stable SABnzbd releases |
unstable | ✅ | Pre-releases from the develop branch |
nightly | ✅ | Latest commits from the develop branch |
Initial setup is done via http://<your-ip>:8080
.
See the SABnzbd wiki for more information.
We have set /incomplete-downloads
and /downloads
as optional paths, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability for atomic moves (TL;DR instant file moves, rather than copy+delete) of files while processing content.
Use the optional paths if you don't understand, or don't want atomic moves. Whichever paths you choose to use, make sure to set the Completed Download Folder
and the Temporary Download Folder
in the SABnzbd gui settings, under Folders
.
The folks over at servarr.com wrote a good write-up on how to get started with this.
This image can be run with a read-only container filesystem. For details please read the docs.
This image can be run with a non-root user. For details please read the docs.
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
[!NOTE] Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.
---
services:
sabnzbd:
image: lscr.io/linuxserver/sabnzbd:latest
container_name: sabnzbd
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /path/to/sabnzbd/config:/config
- /path/to/downloads:/downloads #optional
- /path/to/incomplete/downloads:/incomplete-downloads #optional
ports:
- 8080:8080
restart: unless-stopped
docker run -d \
--name=sabnzbd \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-p 8080:8080 \
-v /path/to/sabnzbd/config:/config \
-v /path/to/downloads:/downloads `#optional` \
-v /path/to/incomplete/downloads:/incomplete-downloads `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/sabnzbd:latest
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal>
respectively. For example, -p 8080:80
would expose port 80
from inside the container to be accessible from the host's IP on port 8080
outside the container.
Parameter | Function |
---|---|
-p 8080:8080 | HTTP port for the WebUI. |
-e PUID=1000 | for UserID - see below for explanation |
-e PGID=1000 | for GroupID - see below for explanation |
-e TZ=Etc/UTC | specify a timezone to use, see this list. |
-v /config | Persistent config files |
-v /downloads | Local path for finished downloads. |
-v /incomplete-downloads | Local path for incomplete-downloads. |
--read-only=true | Run container with a read-only filesystem. Please read the docs. |
--user=1000:1000 | Run container with a non-root user. Please read the docs. |
You can set any environment variable from a file by using a special prepend FILE__
.
As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariable
Will set the environment variable MYVAR
based on the contents of the /run/secrets/mysecretvariable
file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022
setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using 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 any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000
and PGID=1000
, to find yours use id your_user
as below:
id your_user
Example output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
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
Container version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' sabnzbd
Image version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sabnzbd:latest
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Update images:
All images:
docker-compose pull
Single image:
docker-compose pull sabnzbd
Update containers:
All containers:
docker-compose up -d
Single container:
docker-compose up -d sabnzbd
You can also remove the old dangling images:
docker image prune
Update the image:
docker pull lscr.io/linuxserver/sabnzbd:latest
Stop the running container:
docker stop sabnzbd
Delete the container:
docker rm sabnzbd
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config
folder and settings will be preserved)
You can also remove the old dangling images:
docker image prune
[!TIP] We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-sabnzbd.git
cd docker-sabnzbd
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/sabnzbd:latest .
The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64
.
python
to python3
.docker pull linuxserver/sabnzbd