The setup SonarrRadarrSabNZBd on Docker is possible with a singel docker-compose.yml and a simple srs.env. The srs.env is the file where all the configuration settings can be customized to ones setup. This documentation assumes the reader has a basic knowledge of the linux terminal and navigating the filesystem.
- Quick Setup
- Installing Docker on Ubuntu Server PVE
- SOURCES
This QS supposes you already have a docker environement up and running.
Copy the docker compose file and the env file file to a local directory. Make sure that all the paths in the env file file exist and will be reachable for the Docker containers. Fit ports, user- and group-id's and other settings to your environement.
Important: Rename the env file srs.env to .env -> #Wrong ENV file name (take note that naming the env file like that will make it invisible to ls (use "ls -ahl"))
Then you just deploy the docker compose file with:
cd C:\YMLDirector\ (in my case /data/compose)
docker-compose up -dLookup #Not running containers in the background for explanations about -d
Source: Installing Docker and Utils on Ubuntu
A few commands result in a quick and dirty Docker installation.
sudo apt-get update
sudo apt-get install apt-transport-https ca-certificates curl software-properties-common
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository "deb [arch=amd64] \ https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install docker-ceI modified the installation by adding a file daemon.json under /etc/docker/
{
"hosts" : ["unix:///var/run/docker.sock", "tcp://0.0.0.0:2375"],
"data-root" : "/data/docker"
}This was to modify the directory wherein Docker saves its data. -> Also read #System folders
By editing /etc/systemd/system/docker.service.d/override.conf you can then enable the settings from daemon.json. You can edit override.conf with the command systemctl edit docker:
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd
Docker-Compose needs to be downloaded from github and moved to a directory that is in the environement file. You can check these paths with cat /etc/environement
In this case /usr/local/bin is in the environement file and the following commands will download and enable docker-compose to be usable in the Shell Terminal
curl -L https://github.com/docker/compose/releases/download/1.16.1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-composeFollow the instructions from the #Quick Setup chapter with your working environement.
This file defines the different Services and their respective configurations.
Al changable variables are defined in the env file so I will comment on those options which you can then correlate to the docker compose file.
These should be selfexplanatory. The documentation from the the sources provided the image links.
SABNZBDIMG=lscr.io/linuxserver/sabnzbd:latest
SABNZBDCONTAINERNAME=sabnzbdIn the chapter #Configure Docker you are able to define a different storage folder for the docker installation. This enables you to keep all relevant docker data on a secured nas attached over nfs and run the containers on a small and efficient virtual machine.
Therefore all the folders under "#SOFTWARE CONFIGURATION FOLDER VARIABLES" in the env file could also be defined to be on the nas storage, which facilitates a future migration and mitigates the damage caused by the failure of the virtual machine.
srsp = SonarrRadarrSabnzbdPlex
#SOFTWARE CONFIGURATION FOLDER VARIABLES
SABNZBDHOME=/nas/srsp/conf/sabnzbd
SONARRHOME=/nas/srsp/conf/sonarr
RADARRHOME=/nas/srsp/conf/radarr
PLEXHOME=/nas/srsp/conf/plexYou will have to give srs access to your existing or new media libraries. So you will have to setup and mount your external harddrive/s, nas, etc. to the virtual machine with your running docker containers.
I recommend to set all paths under "## Sabnzbd download folders" to a storage space that is directly attached to the machine running the docker containers.
Under "## Media library folders for plex" you have to set the path to the mountpoint of all your media storage spaces. If you have multiple harddrives or nas you would have to mount those under the path defined by "SERIESFOLDER" & "MOVIESFOLDER" like this:
/medialibrary/media/series/
/medialibrary/media/series/nas1 *or hdd1*/series
/medialibrary/media/series/nas2 *or hdd2*/series
/medialibrary/media/series/nas3 *or hdd3*/series# MEDIA FOLDER VARIABLES
## Sabnzbd download folders
DOWNLOADFOLDER=/dev/sda1/usenet/download
COMPLETEDDOWNLOADS=/dev/sdb1/usenet/complete
INCOMPLETEDOWNLOADS=/dev/sdb1/usenet/incomplete
## Media library folders for plex
SERIESFOLDER=/medialibrary/media/series
MOVIESFOLDER=/medialibrary/media/moviesMy OCD kicked in with the srs ports under #PORTS but you could set them to default (you can find the default ports in the docker compose file)
The user and group id's need to be fitted to your system, but if you built a virtual machine just for these services, you can leve them as is.
#PORTS
SABNZBDPORT=8080
SONARRPORT=8989
RADARRPORT=7878
PLEXPORT=32400The plex claim is used to add the plex server to an account. This setting can stay empty. You can get your claim token from https://www.plex.tv/claim/
I had some issues getting the containers running because it would not read my srs.env file. This was due to my missunderstanding about the required filename. The version of docker-compose I installed (1.16.1) did not allow to specify a ENV file. Therefore srs.env needed to be called .env
Here are the contents of the compose directory:
/data/compose ls -a .env docker-compose.yml
The errors I would get if the file .env was called srs.env
root@Usenet:/data/compose# docker-compose up WARNING: The RADARRUID variable is not set. Defaulting to a blank string. WARNING: The RADARRGID variable is not set. Defaulting to a blank string. WARNING: The TIMEZONE variable is not set. Defaulting to a blank string. WARNING: The RADARRHOME variable is not set. Defaulting to a blank string. WARNING: The MOVIESFOLDER variable is not set. Defaulting to a blank string. WARNING: The COMPLETEDDOWNLOADS variable is not set. Defaulting to a blank string. WARNING: The RADARRCONTAINERNAME variable is not set. Defaulting to a blank string. WARNING: The RADARRIMG variable is not set. Defaulting to a blank string. WARNING: The RADARRPORT variable is not set. Defaulting to a blank string. WARNING: The SONARRUID variable is not set. Defaulting to a blank string. WARNING: The SONARRGID variable is not set. Defaulting to a blank string. WARNING: The SONARRHOME variable is not set. Defaulting to a blank string. WARNING: The SERIESFOLDER variable is not set. Defaulting to a blank string. WARNING: The SONARRCONTAINERNAME variable is not set. Defaulting to a blank string. WARNING: The SONARRIMG variable is not set. Defaulting to a blank string. WARNING: The SONARRPORT variable is not set. Defaulting to a blank string. WARNING: The SABNZBDUID variable is not set. Defaulting to a blank string. WARNING: The SABNZBDGID variable is not set. Defaulting to a blank string. WARNING: The SABNZBDHOME variable is not set. Defaulting to a blank string. WARNING: The DOWNLOADFOLDER variable is not set. Defaulting to a blank string. WARNING: The INCOMPLETEDOWNLOADS variable is not set. Defaulting to a blank string. WARNING: The SABNZBDCONTAINERNAME variable is not set. Defaulting to a blank string. WARNING: The SABNZBDIMG variable is not set. Defaulting to a blank string. WARNING: The SABNZBDPORT variable is not set. Defaulting to a blank string. ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the
serviceskey, or omit theversionkey and place your service definitions at the root of the file to use version 1. For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
The Basic command to get a docker-compose.yml up and running is docker-compose up
When working in a terminal over ssh, the command will generate output and enter the docker-compose cli which you can exit with CTRL+C but this will also stopp all containers.
That is why it is necessary to run the docker-compose command with the -d --detached flag so that the containers will be startet in the background.
Solution:
cd C:\YMLDirector\ (in my case /data/compose)
docker-compose up -dExample output without -d flag (note the last lines at the botton)
radarr | [Info] Microsoft.Hosting.Lifetime: Content root path: /app/radarr/bin
sonarr | [Info] SonarrBootstrapper: Starting Web Server
sabnzbd | /usr/lib/python3.9/site-packages/cherrypy/process/servers.py:416: UserWarning: Unable to verify that the server is bound on 8080
sabnzbd | warnings.warn(msg)
sabnzbd | 2022-07-10 17:28:51,631::INFO::[_cplogging:213] [10/Jul/2022:17:28:51] ENGINE Serving on http://:::8080
sabnzbd | 2022-07-10 17:28:51,632::INFO::[_cplogging:213] [10/Jul/2022:17:28:51] ENGINE Bus STARTED
sabnzbd | 2022-07-10 17:28:51,633::INFO::[SABnzbd:1474] Starting SABnzbd.py-3.6.0
sabnzbd | 2022-07-10 17:28:51,645::INFO::[dirscanner:117] Dirscanner starting up
sabnzbd | 2022-07-10 17:28:51,646::INFO::[panic:239] Launching browser with http://127.0.0.1:8080/sabnzbd
sabnzbd | 2022-07-10 17:28:51,648::INFO::[notifier:123] Sending notification: SABnzbd - SABnzbd 3.6.0 started (type=startup, job_cat=None)
sabnzbd | 2022-07-10 17:28:52,002::INFO::[zconfig:61] No bonjour/zeroconf support installed
sabnzbd | 2022-07-10 17:28:52,004::INFO::[ssdp:108] Serving SSDP on 172.18.0.3 as SABnzbd
^CGracefully stopping... (press Ctrl+C again to force)
Stopping radarr ... done
Stopping sabnzbd ... done
Stopping sonarr ... done
linuxserver/sabnzbd linuxserver/plex linuxserver/radarr linuxserver/sonarr Installing Docker and Utils on Ubuntu