Skip to content

Setting up NZB Hydra in Docker on a Synology NAS

Updated for DSM6 and the latest version of Docker 19/11/2016

Further update 17/01/2017

Thanks to Chad in the comments, he found how to get around the current issue where the version of Hydra installed on DSM6.0 devices is out of date, a quick run down of the issue is that the version of Docker currently used on DSM6.0 uses the old v1 API to get hold of the versions of images available. This means the latest version you can get of Hydra is ’10’. This issue is fixed in DSM6.1 which uses the v2 of the docker API. I have amended the guide below accordingly

In this guide I will be taking you through the steps to download and setup NZB Hydra in Docker on a Synology NAS, this makes some assumptions that you know your way around the DSM interface and have already read one of my previous guides.

NZB Hydra combines all your various indexers into a single search site, this can then be fed into Couchpotato, Sonarr etc. This means you only need to update the single application whenever you want to add a new indexer rather than each one individually.

Downloading the container

DSM6.0 Users

Login to your Diskstation via SSH and then enter ‘sudo docker pull linuxserver/hydra’ this will download the latest version of the Hydra container, it will appear in the list of available containers immediately at the time of writing its just 73mb compared to the old version which is 700mb, you can now skip to PGID and PUID section.


DSM6.1+ Users
So first up we need to grab the container as per my other guides we are using the Linux|Server version as these work great.

Open up Docker within DSM and navigate to the ‘Registry’ section and search for Hydra in the keyword box. Right click and download the Linux|Server version. When it asks which version number you want to use just choose latest this will ensure the container updates to new versions when they are released.

Hydra01

If you now go to the ‘Image’ section you will see the container downloading.

Hydra02

PGID and PUID

In the previous versions of these guides I used a long winded approach to getting your ID information, I have since found a much easier approach.

You will need to SSH into your Diskstation using ‘Putty’ or an equivalent program.

Open up Putty, the only thing you need to enter is the IP address of your NAS and select the SSH radio button.

putty

Click on open, you will get a prompt asking if you trust the key, if this is the first time you have used SSH, just press OK or accept.

Enter the login information for you Synology user account, you will not be able to see the password as you type it, I use a very long one so I just paste it in from my password manager. (right click acts as paste in putty)

Once logged in type ‘id’ without the quotes and this will show your UID(aka PUID) which in my case is 1026 and the GID(aka PGID) which is 101 for an administrator

putty02

Setting up the container

Back in the ‘Image’ menu highlight the NZB Hydra container and click on Launch. This will open up the setup wizard.

On the first screen I am not making any changes as I do not need to limit the resources on my 1815+ as I have 6GB of RAM, just go straight into ‘Advanced Settings’.

Tick the ‘Enable Auto Restart’ this will ensure the container starts up automatically if you reboot.

Hydra04

On the ‘Volume’ tab you need to add the paths to where you want to keep the config files and where you want to place any NZBs grabbed by using Hydra directly.

I always use the Docker folder and then a sub-directory for all configs.

Hydra05

Skip the ‘Network’ tab

Next is the ‘Port Settings’ tab you will need to change the Auto setting to either the identical port number 5075 or change it to a custom one if you want to. This is the port you will use to access the Hydra container.

Hydra06

Last up is the PGID and PUID that we made note of earlier in the guide.

Hydra07

Click on OK to get back to the main menu and then click on next, tick the ‘Run this container after the wizard has finished’ and hit ‘Apply’

The container should now start up, this can be seen in the ‘Container’ tab as the RAM and CPU usage should fluctuate as it starts, its worth giving it a minute or so on its first launch just in case it needs to download any updates during boot. You should then be able to access the interface via your Synology IP and the port number you chose earlier.

hydrafeature

Published inDockerSynology

13 Comments

  1. Sapan Parikh Sapan Parikh

    Gerat Post Dr, Frankenstein! Did you have a guide for Plex?

    • Dr_Frankenstein Dr_Frankenstein

      It’s in the works as I am just working out some issues with the install, as some of the ports clash with the default ones used by Audiostation.

      • Sapan Parikh Sapan Parikh

        nice! will keep an out for it..

      • Angelus Angelus

        PMS would be great, i want to use it as a database of course, i don’t think with transcoding it would be fast enough but with an player like infuse i think it will work great.

        Thx for all the hard work, your site helped me a lot how it works and understanding why it’s so much better.

  2. kwartet kwartet

    Thank you for the guide. Although it’s mostly the same process every time, I still appreciate the guide(s)! Working out all the paths needed can be difficult by yourself. I have not heard of this application before, certainly gonna give it a try. Thank you and keep up the good work!

    • Dr_Frankenstein Dr_Frankenstein

      No problem they are pretty much the same each time but was thinking people would like to be following something specific to there needs.

  3. chris chris

    Hi, I followed the guide and everything is working, except nzbhydra is only available on the local port, not the container port and the local port changes every time.. Any suggestions to get this to work on the container port?

    • Dr_Frankenstein Dr_Frankenstein

      For hydra I think I just set the both to the same ports

  4. Chad Chad

    I’ve followed the guide and am unable to apply updates as they are released. The following is seen in the logs.

    error: Your local changes to the following files would be overwritten by merge:

    followed by the reference to quite a few files

    Please, commit your changes or stash them before you can merge.
    Aborting

    After some digging I’ve found that the only way to apply updates is to manually delete the files and running git pull from a terminal.

    Thoughts?

    • Dr_Frankenstein Dr_Frankenstein

      I actually have the same issue and have not tried to fix it as everything seems to be working as it should. I think this is a problem with the container. I am always in the Linux|Server IRC channel I will see if they can shed any more light

      • Chad Chad

        Thanks, that’d be great!

  5. Chad Chad

    Sorry for the delay in getting this posted after we spoke on IRC. Here’s what information I gathered on it, and how to get around it.

    It would seem it’s an issue with the Synology Docker app not showing all of the updates that are available, talked about in link 1 below. When you try to download it prompts, 10 is the latest I see yet if you look here at link 2 below, you’ll see it’s not the latest. What you have to do is SSH into your Synology, and execute sudo docker pull linuxserver/hydra and it will automatically pull the latest and the problem I mentioned in the earlier post will be solved.

    1: https://blog.jstubberfield.net/so-docker-in-your-synology-isnt-showing-latest-tags-2/

    2: https://hub.docker.com/r/linuxserver/hydra/tags/

    • Dr_Frankenstein Dr_Frankenstein

      Thanks for getting back, this is great information. I am going to add this to the end of the guide.

Leave a Reply

Your email address will not be published. Required fields are marked *