https://linuxserver.io

The LinuxServer.io team brings you another container release easy user mapping and community support. Find us for support at:

  • forum.linuxserver.io
  • IRC on freenode at #linuxserver.io
  • Podcast covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!

linuxserver/sabnzbd

[Docker Pulls][hub][Docker Stars][hub]Build Status [hub]: https://hub.docker.com/r/linuxserver/sabnzbd/

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. This container includes par2 multicore.

[sabnzbd][saburl] [saburl]: http://sabnzbd.org/

Usage

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

Parameters

  • -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 /downloads local path for finished downloads
  • -v /incomplete-downloads local path for incomplete-downloads - optional
  • -e PGID for GroupID - see below for explanation
  • -e PUID for UserID - see below for explanation
  • -e TZ for setting timezone information, eg Europe/London

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 PUID=1001 and 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

Info

  • 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

Versions

  • 28.08.16: Rebase to xenial.
  • 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.
S
Description
No description provided
Readme GPL-3.0
1.9 MiB
Languages
Dockerfile 71.5%
Shell 28.5%