arrX

Create multiple (Sonarr / Radarr / Bazarr) containers

Read through this entire page, even if you are only installing one of the apps. The instructions at the bottom of the page assume you have read the material at the top of the page.

NOTE: the names have to be compliant with both domain names and docker names, so no funny business. Do not use anything but a-z and 0-9, no spaces, no commas, no colons, no dash, no exclamation marks, no nothing!

ALSO NOTE: All apps will prefix subdomain and docker container names with the name of the app. For example the subdomain and names of sonarr's docker containers will, with the default settings, be sonarr1080webdl and sonarr1080remux.

There is nothing magic about the example configs [1080webdl, 1080remux] given below. They represent some common use cases, but you can use whatever names you wish.

In general terms:

appname:
  roles: ["", bing, bang. boing]

will create:

• appname
• appnamebing
• appnamebang
• appnameboing

as docker containers, subdomain, and data directories in /opt

You will need to configure these new containers just as you did the stock containers. One change; be sure each one gets a unique download category, so that each instance imports only those downloads meant for it.

Also, you probably want to put some thought into the directory and library structure you want to use. See "Customizing Plex Libraries".

Create multiple Sonarr v3 container

1. Edit settings.yml and change the sonarrx roles to what you want:

   NOTE: "" is to create sonarr.domain.com so remember to stop & remove any existing Cloudbox containers if you want to use SonarrX exclusively instead of the included Cloudbox ones. If you do NOT want that to happen, leave that empty entry out of this config.

   sonarrx:
     roles: ["", 1080webdl, 1080remux]

2. Run the sonarrx role as a normal community role.

   cd ~/community
   sudo ansible-playbook community.yml --tags sonarrx

Create multiple Radarr containers

1. Edit settings.yml and change the radarrx roles to what you want:

   NOTE: "" is to create radarr.domain.com so remember to stop & remove any existing Cloudbox containers if you want to use RadarrX exclusively instead of the included Cloudbox ones. If you do NOT want that to happen, leave that empty entry out of this config.

   radarrx:
    roles: ["", 1080webdl, 1080remux]

2. Run the radarrx role as a normal community role.

   cd ~/community
   sudo ansible-playbook community.yml --tags radarrx

Create multiple Bazarr containers

1. Edit settings.yml and change the bazarrx roles to what you want:

   NOTE: "" is to create bazarr.domain.com so remember to stop & remove any existing Cloudbox containers if you want to use BazarrX exclusively instead of the included Cloudbox ones. If you do NOT want that to happen, leave that empty entry out of this config.

   bazarrx:
    roles: ["", 1080webdl, 1080remux]
   

2. Run the bazarrx role as a normal community role.

   cd ~/community
   sudo ansible-playbook community.yml --tags bazarrx

Create a single Bazarr container

1. Edit settings.yml and change the bazarrx roles to what you want:

   bazarrx:
    roles: [""]
   

2. Run the bazarrx role as a normal community role.

   cd ~/community
   sudo ansible-playbook community.yml --tags bazarrx

Get Sonarr4k and Radarr4k Containers Again

1. Edit settings.yml.

2. Add the following:

   sonarrx:
    roles: [4k]
   radarrx:
    roles: [4k]

3. Run the following tags:

   cd ~/community
   sudo ansible-playbook community.yml --tags sonarrx,radarrx

4. Containers should be up and running again. With the same paths as were setup with CB, i.e. your data will have been migrated over if you had the original "radarrx" and "sonarrx" installed.

Tips

Radarr

Caching

If you use NZBHydra2 as an indexer in Radarr create a duplicate entry with caching enabled as an additional parameter. Repeat for Sonarr.