You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://microbadger.com/images/linuxserver/hydra2"Get your own version badge on microbadger.com")
[](https://microbadger.com/images/linuxserver/nzbhydra2"Get your own version badge on microbadger.com")
[Hydra2](https://github.com/theotherp/nzbhydra2) is a meta search application for NZB indexers, the "spiritual successor" to NZBmegasearcH, and an evolution of the original application [NZBHydra](https://github.com/theotherp/nzbhydra).
39
+
[Nzbhydra2](https://github.com/theotherp/nzbhydra2) is a meta search application for NZB indexers, the "spiritual successor" to NZBmegasearcH, and an evolution of the original application [NZBHydra](https://github.com/theotherp/nzbhydra).
40
40
41
-
It provides easy access to a number of raw and newznab based indexers. The application NZBHydra 2 is replacing NZBHydra 1 and supports migrating from V1. Be wary that there may be some compatibility issues for those migrating from V1 to V2, so ensure you back up your old configuration before moving over to the new version. **NOTE:** The last version that supports migration is `linuxserver/hydra2:v2.10.2-ls49`
41
+
It provides easy access to a number of raw and newznab based indexers. The application NZBHydra 2 is replacing NZBHydra 1 and supports migrating from V1. Be wary that there may be some compatibility issues for those migrating from V1 to V2, so ensure you back up your old configuration before moving over to the new version. **NOTE:** The last version that supports migration is `linuxserver/nzbhydra2:v2.10.2-ls49`
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](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
49
49
50
-
Simply pulling `linuxserver/hydra2` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
50
+
Simply pulling `linuxserver/nzbhydra2` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
51
51
52
52
The architectures supported by this image are:
53
53
@@ -74,15 +74,15 @@ Here are some example snippets to help you get started creating a container.
74
74
75
75
```
76
76
docker create \
77
-
--name=hydra2 \
77
+
--name=nzbhydra2 \
78
78
-e PUID=1000 \
79
79
-e PGID=1000 \
80
80
-e TZ=Europe/London \
81
81
-p 5076:5076 \
82
82
-v <path to data>:/config \
83
83
-v <nzb download>:/downloads \
84
84
--restart unless-stopped \
85
-
linuxserver/hydra2
85
+
linuxserver/nzbhydra2
86
86
```
87
87
88
88
@@ -94,9 +94,9 @@ Compatible with docker-compose v2 schemas.
94
94
---
95
95
version: "2.1"
96
96
services:
97
-
hydra2:
98
-
image: linuxserver/hydra2
99
-
container_name: hydra2
97
+
nzbhydra2:
98
+
image: linuxserver/nzbhydra2
99
+
container_name: nzbhydra2
100
100
environment:
101
101
- PUID=1000
102
102
- PGID=1000
@@ -119,7 +119,7 @@ Container images are configured using parameters passed at runtime (such as thos
119
119
|`-e PUID=1000`| for UserID - see below for explanation |
120
120
|`-e PGID=1000`| for GroupID - see below for explanation |
121
121
|`-e TZ=Europe/London`| Specify a timezone to use EG Europe/London. |
122
-
|`-v /config`| Where hydra2 should store config files. |
122
+
|`-v /config`| Where nzbhydra2 should store config files. |
123
123
|`-v /downloads`| NZB download folder. |
124
124
125
125
## Environment variables from files (Docker secrets)
@@ -155,19 +155,19 @@ The web interface is at `<your ip>:5076` , to set up indexers and connections to
155
155
156
156
157
157
## Docker Mods
158
-
[](https://mods.linuxserver.io/?mod=hydra2"view available mods for this container.")
158
+
[](https://mods.linuxserver.io/?mod=nzbhydra2"view available mods for this container.")
159
159
160
160
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
161
161
162
162
163
163
## Support Info
164
164
165
-
* Shell access whilst the container is running: `docker exec -it hydra2 /bin/bash`
166
-
* To monitor the logs of the container in realtime: `docker logs -f hydra2`
165
+
* Shell access whilst the container is running: `docker exec -it nzbhydra2 /bin/bash`
166
+
* To monitor the logs of the container in realtime: `docker logs -f nzbhydra2`
167
167
* container version number
168
-
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' hydra2`
168
+
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' nzbhydra2`
169
169
* image version number
170
-
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/hydra2`
170
+
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/nzbhydra2`
171
171
172
172
## Updating Info
173
173
@@ -176,18 +176,18 @@ Most of our images are static, versioned, and require an image update and contai
176
176
Below are the instructions for updating containers:
177
177
178
178
### Via Docker Run/Create
179
-
* Update the image: `docker pull linuxserver/hydra2`
180
-
* Stop the running container: `docker stop hydra2`
181
-
* Delete the container: `docker rm hydra2`
179
+
* Update the image: `docker pull linuxserver/nzbhydra2`
180
+
* Stop the running container: `docker stop nzbhydra2`
181
+
* Delete the container: `docker rm nzbhydra2`
182
182
* Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
183
-
* Start the new container: `docker start hydra2`
183
+
* Start the new container: `docker start nzbhydra2`
184
184
* You can also remove the old dangling images: `docker image prune`
185
185
186
186
### Via Docker Compose
187
187
* Update all images: `docker-compose pull`
188
-
* or update a single image: `docker-compose pull hydra2`
188
+
* or update a single image: `docker-compose pull nzbhydra2`
189
189
* Let compose update all containers as necessary: `docker-compose up -d`
190
-
* or update a single container: `docker-compose up -d hydra2`
190
+
* or update a single container: `docker-compose up -d nzbhydra2`
191
191
* You can also remove the old dangling images: `docker image prune`
192
192
193
193
### Via Watchtower auto-updater (especially useful if you don't remember the original parameters)
@@ -196,7 +196,7 @@ Below are the instructions for updating containers:
196
196
docker run --rm \
197
197
-v /var/run/docker.sock:/var/run/docker.sock \
198
198
containrrr/watchtower \
199
-
--run-once hydra2
199
+
--run-once nzbhydra2
200
200
```
201
201
202
202
**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
@@ -207,12 +207,12 @@ Below are the instructions for updating containers:
207
207
208
208
If you want to make local modifications to these images for development purposes or just to customize the logic:
0 commit comments