kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Templated Files
LinuxServer-CI
rodzic
2f37e5e09b
commit
c02ba5f6ea
|
|
@ -1,85 +1,139 @@
|
|||
[linuxserverurl]: https://linuxserver.io
|
||||
[forumurl]: https://forum.linuxserver.io
|
||||
[ircurl]: https://www.linuxserver.io/irc/
|
||||
[podcasturl]: https://www.linuxserver.io/podcast/
|
||||
[appurl]: https://github.com/theotherp/nzbhydra2
|
||||
[hub]: https://hub.docker.com/r/linuxserver/hydra2/
|
||||
# [linuxserver/hydra2](https://github.com/linuxserver/docker-hydra2)
|
||||
|
||||
[][linuxserverurl]
|
||||
[](https://discord.gg/YWrKVTn)
|
||||
[](https://microbadger.com/images/linuxserver/hydra2 "Get your own version badge on microbadger.com")
|
||||
[](https://microbadger.com/images/linuxserver/hydra2 "Get your own version badge on microbadger.com")
|
||||
|
||||
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-hydra2/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/hydra2/latest/index.html)
|
||||
|
||||
The [LinuxServer.io][linuxserverurl] team brings you another container release featuring easy user mapping and community support. Find us for support at:
|
||||
* [forum.linuxserver.io][forumurl]
|
||||
* [IRC][ircurl] on freenode at `#linuxserver.io`
|
||||
* [Podcast][podcasturl] covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!
|
||||
[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).
|
||||
|
||||
# linuxserver/hydra2
|
||||
[](https://microbadger.com/images/linuxserver/hydra2 "Get your own version badge on microbadger.com")[](https://microbadger.com/images/linuxserver/hydra2 "Get your own image badge on microbadger.com")[][hub][][hub][](https://ci.linuxserver.io/job/Docker-Builders/job/x86-64/job/x86-64-hydra2/)
|
||||
It provides easy access to a number of raw and newznab based indexers. The application NZBHydra 2 is currently in its early stages and is in active development. 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.
|
||||
|
||||
_NZBHydra 2_ 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)_ . It provides easy access to a number of raw and newznab based indexers.
|
||||
|
||||
The application NZBHydra 2 is currently in its early stages and is in active development. 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.
|
||||
## 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](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).
|
||||
|
||||
Simply pulling `linuxserver/hydra2` 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:
|
||||
|
||||
| Architecture | Tag |
|
||||
| :----: | --- |
|
||||
| x86-64 | amd64-latest |
|
||||
| arm64 | arm64v8-latest |
|
||||
| armhf | arm32v6-latest |
|
||||
|
||||
[][appurl]
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker
|
||||
|
||||
```
|
||||
docker create --name=hydra2 \
|
||||
-v <path to data>:/config \
|
||||
-v <nzb download>:/downloads \
|
||||
-e PGID=<gid> -e PUID=<uid> \
|
||||
-e TZ=<timezone> \
|
||||
-p 5076:5076 linuxserver/hydra2
|
||||
docker create \
|
||||
--name=hydra2 \
|
||||
-e PUID=1001 \
|
||||
-e PGID=1001 \
|
||||
-e TZ=Europe/London \
|
||||
-p 5076:5076 \
|
||||
-v <path to data>:/config \
|
||||
-v <nzb download>:/downloads \
|
||||
--restart unless-stopped \
|
||||
linuxserver/hydra2
|
||||
```
|
||||
|
||||
|
||||
### docker-compose
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
||||
```yaml
|
||||
---
|
||||
version: "2"
|
||||
services:
|
||||
hydra2:
|
||||
image: linuxserver/hydra2
|
||||
container_name: hydra2
|
||||
environment:
|
||||
- PUID=1001
|
||||
- PGID=1001
|
||||
- TZ=Europe/London
|
||||
volumes:
|
||||
- <path to data>:/config
|
||||
- <nzb download>:/downloads
|
||||
ports:
|
||||
- 5076:5076
|
||||
mem_limit: 4096m
|
||||
restart: unless-stopped
|
||||
```
|
||||
|
||||
## Parameters
|
||||
|
||||
`The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.
|
||||
For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container.
|
||||
So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080
|
||||
http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.`
|
||||
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`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :----: | --- |
|
||||
| `5076` | WebUI |
|
||||
|
||||
|
||||
* `-p 5076` - the port(s)
|
||||
* `-v /config` - Where hydra2 should store config files
|
||||
* `-v /downloads` - NZB download folder
|
||||
* `-e PGID` for GroupID - see below for explanation
|
||||
* `-e PUID` for UserID - see below for explanation
|
||||
* `-e TZ` for timezone EG. Europe/London
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
It is based on ubuntu bionic with s6 overlay, for shell access whilst the container is running do `docker exec -it hydra2 /bin/bash`.
|
||||
| Env | Function |
|
||||
| :----: | --- |
|
||||
| `PUID=1001` | for UserID - see below for explanation |
|
||||
| `PGID=1001` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
|
||||
|
||||
### User / Group Identifiers
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
Sometimes when using data 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 the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
|
||||
| Volume | Function |
|
||||
| :----: | --- |
|
||||
| `/config` | Where hydra2 should store config files. |
|
||||
| `/downloads` | NZB download folder. |
|
||||
|
||||
In this instance `PUID=1001` and `PGID=1001`. To find yours use `id user` as below:
|
||||
|
||||
|
||||
## 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=1001` and `PGID=1001`, to find yours use `id user` as below:
|
||||
|
||||
```
|
||||
$ id <dockeruser>
|
||||
$ id username
|
||||
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
|
||||
```
|
||||
|
||||
## Setting up the application
|
||||
## Application Setup
|
||||
|
||||
The web interface is at `<your ip>:5076` , to set up indexers and connections to your nzb download applications.
|
||||
|
||||
|
||||
## Info
|
||||
|
||||
* To monitor the logs of the container in realtime `docker logs -f hydra2`.
|
||||
## Support Info
|
||||
|
||||
* container version number
|
||||
|
||||
`docker inspect -f '{{ index .Config.Labels "build_version" }}' hydra2`
|
||||
|
||||
* image version number
|
||||
|
||||
`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/hydra2`
|
||||
* Shell access whilst the container is running:
|
||||
* `docker exec -it hydra2 /bin/bash`
|
||||
* To monitor the logs of the container in realtime:
|
||||
* `docker logs -f hydra2`
|
||||
* Container version number
|
||||
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' hydra2`
|
||||
* Image version number
|
||||
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/hydra2`
|
||||
|
||||
## Versions
|
||||
|
||||
+ **18.08.18:** Bump java version to 10, (bionic currently refers to it as version 11).
|
||||
+ **10.08.18:** Rebase to ubuntu bionic.
|
||||
+ **15.04.18:** Change to port 5076 in the Dockerfile.
|
||||
+ **11.01.18:** Initial Release.
|
||||
* **11.02.19:** - Add pipeline logic and multi arch.
|
||||
* **18.08.18:** - Bump java version to 10, (bionic currently refers to it as version 11).
|
||||
* **10.08.18:** - Rebase to ubuntu bionic.
|
||||
* **15.04.18:** - Change to port 5076 in the Dockerfile.
|
||||
* **11.01.18:** - Initial Release.
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue