​​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​​

​Hydra is a meta search for NZB indexers and the "spiritual successor" to NZBmegasearcH. It provides easy access to a number of raw and newznab based indexers.

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling ghcr.io/linuxserver/hydra 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:

Usage

Here are some example snippets to help you get started creating a container from this image.

docker-compose (recommended)

Compatible with docker-compose v2 schemas.

---
version: "2.1"
services:
  hydra:
    image: ghcr.io/linuxserver/hydra
    container_name: hydra
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - <path to data>:/config
      - <nzb download>:/downloads
    ports:
      - 5075:5075
    restart: unless-stopped

docker cli

docker run -d \
  --name=hydra \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 5075:5075 \
  -v <path to data>:/config \
  -v <nzb download>:/downloads \
  --restart unless-stopped \
  ghcr.io/linuxserver/hydra

Parameters

Docker images 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.

Ports (-p)

Environment Variables (-e)

Volume Mappings (-v)

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

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.

User / Group Identifiers

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 user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Application Setup

THIS IMAGE HAS BEEN DEPRECATED.

Please use linuxserver/nzbhydra2 instead.

The web interface is at <your ip>:5075 , to set up indexers and connections to your nzb download applications.

Docker Mods

​​​ ​​​

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.

Support Info

• Shell access whilst the container is running:

  • docker exec -it hydra /bin/bash

• To monitor the logs of the container in realtime:

  • docker logs -f hydra

• Container version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' hydra

• Image version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/hydra

Versions

• 04.11.19: - Deprecated. Please use linuxserver/nzbhydra2 instead.

• 19.12.19: - Rebasing to alpine 3.11.

• 28.06.19: - Rebasing to alpine 3.10.

• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.

• 22.02.19: - Rebasing to alpine 3.9.

• 11.02.19: - Add pipeline logic and multi arch.

• 17.08.18: - Rebase to alpine 3.8.

• 12.12.17: - Rebase to alpine 3.7.

• 20.07.17: - Internal git pull instead of at runtime.

• 25.05.17: - Rebase to alpine 3.6.

• 07.11.16: - Move git clone internal to the container,point config, database and log to use same locations for existing users.

• 14.10.16: - Add version layer information.

• 09.09.16: - Add layer badges to README.

• 28.08.16: - Add badges to README.

• 08.08.16: - Rebase to alpine linux.

• 25.01.16: - Initial Release.