|
|
|
@@ -1,5 +1,5 @@
|
|
|
|
|
<!-- DO NOT EDIT THIS FILE MANUALLY -->
|
|
|
|
|
<!-- Please read the CONTRIBUTING.md -->
|
|
|
|
|
<!-- Please read the https://github.com/linuxserver/docker-radarr/blob/nightly/.github/CONTRIBUTING.md -->
|
|
|
|
|
|
|
|
|
|
[](https://linuxserver.io)
|
|
|
|
|
|
|
|
|
@@ -12,13 +12,14 @@
|
|
|
|
|
|
|
|
|
|
The [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring:
|
|
|
|
|
|
|
|
|
|
* regular and timely application updates
|
|
|
|
|
* easy user mappings (PGID, PUID)
|
|
|
|
|
* custom base image with s6 overlay
|
|
|
|
|
* weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
|
|
|
|
|
* regular security updates
|
|
|
|
|
* regular and timely application updates
|
|
|
|
|
* easy user mappings (PGID, PUID)
|
|
|
|
|
* custom base image with s6 overlay
|
|
|
|
|
* weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
|
|
|
|
|
* regular security updates
|
|
|
|
|
|
|
|
|
|
Find us at:
|
|
|
|
|
|
|
|
|
|
* [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
|
|
|
|
|
* [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team.
|
|
|
|
|
* [Discourse](https://discourse.linuxserver.io) - post on our community forum.
|
|
|
|
@@ -40,7 +41,6 @@ Find us at:
|
|
|
|
|
|
|
|
|
|
[Radarr](https://github.com/Radarr/Radarr) - A fork of Sonarr to work with movies à la Couchpotato.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[](https://github.com/Radarr/Radarr)
|
|
|
|
|
|
|
|
|
|
## Supported Architectures
|
|
|
|
@@ -67,6 +67,14 @@ This image provides various versions that are available via tags. `latest` tag u
|
|
|
|
|
| develop | Radarr releases from their develop branch |
|
|
|
|
|
| nightly | Nightly Radarr releases |
|
|
|
|
|
|
|
|
|
|
## Application Setup
|
|
|
|
|
|
|
|
|
|
Access the webui at `<your-ip>:7878`, for more information check out [Radarr](https://github.com/Radarr/Radarr).
|
|
|
|
|
|
|
|
|
|
**Special Note**: Following our current folder structure will result in an inability to hardlink from your downloads to your movies folder because they are on seperate volumes. To support hardlinking, ensure that the movies and downloads data are on a single volume. For example, if you have `/mnt/storage/Movies` and `/mnt/storage/downloads/completed/Movies`, you would want something like `/mnt/storage:/media` for your volume. Then you can hardlink from `/media/downloads/completed` to `/media/Movies`.
|
|
|
|
|
|
|
|
|
|
Another item to keep in mind, is that within Radarr itself, you should map your download client folder to your radarr folder. Navigate to **Settings -> Download Client -> Advanced Settings -> Remote Path Mappings**. Add a new mapping, and set: the Host as the same entry of the Host in your download client (for example its IP address), the Remote Path as `/downloads/Movies` (relative to the internal container path), and Local Path as `/media/downloads/completed/Movies`, assuming you have folders to separate your downloaded data types.
|
|
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
Here are some example snippets to help you get started creating a container.
|
|
|
|
@@ -97,7 +105,7 @@ services:
|
|
|
|
|
|
|
|
|
|
### docker cli
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
```bash
|
|
|
|
|
docker run -d \
|
|
|
|
|
--name=radarr \
|
|
|
|
|
-e PUID=1000 \
|
|
|
|
@@ -111,7 +119,6 @@ docker run -d \
|
|
|
|
|
ghcr.io/linuxserver/radarr
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Parameters
|
|
|
|
|
|
|
|
|
|
Container 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.
|
|
|
|
@@ -132,7 +139,7 @@ You can set any environment variable from a file by using a special prepend `FIL
|
|
|
|
|
|
|
|
|
|
As an example:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
```bash
|
|
|
|
|
-e FILE__PASSWORD=/run/secrets/mysecretpassword
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
@@ -151,28 +158,17 @@ Ensure any volume directories on the host are owned by the same user you specify
|
|
|
|
|
|
|
|
|
|
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
```bash
|
|
|
|
|
$ id username
|
|
|
|
|
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Application Setup
|
|
|
|
|
|
|
|
|
|
Access the webui at `<your-ip>:7878`, for more information check out [Radarr](https://github.com/Radarr/Radarr).
|
|
|
|
|
|
|
|
|
|
**Special Note**: Following our current folder structure will result in an inability to hardlink from your downloads to your movies folder because they are on seperate volumes. To support hardlinking, ensure that the movies and downloads data are on a single volume. For example, if you have `/mnt/storage/Movies` and `/mnt/storage/downloads/completed/Movies`, you would want something like `/mnt/storage:/media` for your volume. Then you can hardlink from `/media/downloads/completed` to `/media/Movies`.
|
|
|
|
|
|
|
|
|
|
Another item to keep in mind, is that within Radarr itself, you should map your download client folder to your radarr folder. Navigate to **Settings -> Download Client -> Advanced Settings -> Remote Path Mappings**. Add a new mapping, and set: the Host as the same entry of the Host in your download client (for example its IP address), the Remote Path as `/downloads/Movies` (relative to the internal container path), and Local Path as `/media/downloads/completed/Movies`, assuming you have folders to separate your downloaded data types.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Docker Mods
|
|
|
|
|
|
|
|
|
|
[](https://mods.linuxserver.io/?mod=radarr "view available mods for this container.") [](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
|
|
|
|
|
|
|
|
|
|
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) 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 radarr /bin/bash`
|
|
|
|
@@ -189,6 +185,7 @@ Most of our images are static, versioned, and require an image update and contai
|
|
|
|
|
Below are the instructions for updating containers:
|
|
|
|
|
|
|
|
|
|
### Via Docker Compose
|
|
|
|
|
|
|
|
|
|
* Update all images: `docker-compose pull`
|
|
|
|
|
* or update a single image: `docker-compose pull radarr`
|
|
|
|
|
* Let compose update all containers as necessary: `docker-compose up -d`
|
|
|
|
@@ -196,6 +193,7 @@ Below are the instructions for updating containers:
|
|
|
|
|
* You can also remove the old dangling images: `docker image prune`
|
|
|
|
|
|
|
|
|
|
### Via Docker Run
|
|
|
|
|
|
|
|
|
|
* Update the image: `docker pull ghcr.io/linuxserver/radarr`
|
|
|
|
|
* Stop the running container: `docker stop radarr`
|
|
|
|
|
* Delete the container: `docker rm radarr`
|
|
|
|
@@ -203,24 +201,29 @@ Below are the instructions for updating containers:
|
|
|
|
|
* You can also remove the old dangling images: `docker image prune`
|
|
|
|
|
|
|
|
|
|
### Via Watchtower auto-updater (only use if you don't remember the original parameters)
|
|
|
|
|
|
|
|
|
|
* Pull the latest image at its tag and replace it with the same env variables in one run:
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
docker run --rm \
|
|
|
|
|
-v /var/run/docker.sock:/var/run/docker.sock \
|
|
|
|
|
containrrr/watchtower \
|
|
|
|
|
--run-once radarr
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
* You can also remove the old dangling images: `docker image prune`
|
|
|
|
|
|
|
|
|
|
**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](https://docs.linuxserver.io/general/docker-compose).
|
|
|
|
|
|
|
|
|
|
### Image Update Notifications - Diun (Docker Image Update Notifier)
|
|
|
|
|
|
|
|
|
|
* We recommend [Diun](https://crazymax.dev/diun/) for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
|
|
|
|
|
|
|
|
|
|
## Building locally
|
|
|
|
|
|
|
|
|
|
If you want to make local modifications to these images for development purposes or just to customize the logic:
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
git clone https://github.com/linuxserver/docker-radarr.git
|
|
|
|
|
cd docker-radarr
|
|
|
|
|
docker build \
|
|
|
|
@@ -230,7 +233,8 @@ docker build \
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
docker run --rm --privileged multiarch/qemu-user-static:register --reset
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
LinuxServer-CI