hotio/unpackerr
Starting the container¶
CLI:
docker run --rm \
--name unpackerr \
-e PUID=1000 \
-e PGID=1000 \
-e UMASK=002 \
-e TZ="Etc/UTC" \
-e ARGS="" \
-e DEBUG="no" \
-e UN_SONARR_0_URL="http://sonarr:8989" \
-e UN_SONARR_0_API_KEY="<yourapikey>" \
-e UN_RADARR_0_URL="http://radarr:7878" \
-e UN_RADARR_0_API_KEY="<yourapikey>" \
-e UN_LIDARR_0_URL="http://lidarr:8686" \
-e UN_LIDARR_0_API_KEY="<yourapikey>" \
-v /<host_folder_config>:/config \
-v /<host_folder_downloads>:/downloads \
hotio/unpackerr
Compose:
version: "3.7"
services:
unpackerr:
container_name: unpackerr
image: hotio/unpackerr
environment:
- PUID=1000
- PGID=1000
- UMASK=002
- TZ=Etc/UTC
- ARGS
- DEBUG=no
- UN_SONARR_0_URL=http://sonarr:8989
- UN_SONARR_0_API_KEY=<yourapikey>
- UN_RADARR_0_URL=http://radarr:7878
- UN_RADARR_0_API_KEY=<yourapikey>
- UN_LIDARR_0_URL=http://lidarr:8686
- UN_LIDARR_0_API_KEY=<yourapikey>
volumes:
- /<host_folder_config>:/config
- /<host_folder_downloads>:/downloads
Tags¶
Tag | Upstream | Version | Build |
---|---|---|---|
release (latest) |
GitHub releases | ||
testing |
GitHub pre-releases | ||
nightly |
Every commit to master branch |
You can also find tags that reference a commit or version number.
Configuration¶
You can use docker environment variables or a configuration file that should be stored in /config/app/unpackerr.conf
. Don't forget to mount your volume where Unpackerr should look to find your downloads. You should use the same volume as is used in the Sonarr/Radarr/Lidarr containers. More advanced configuration methods are possible too, but take a look at the upstream project page for more info on that.
Executing your own scripts¶
If you have a need to do additional stuff when the container starts or stops, you can mount your script with the volume /docker/host/my-script.sh:/etc/cont-init.d/99-my-script
to execute your script on container start or /docker/host/my-script.sh:/etc/cont-finish.d/99-my-script
to execute it when the container stops. An example script can be seen below.
#!/usr/bin/with-contenv bash
echo "Hello, this is me, your script."
Troubleshooting a problem¶
By default all output is redirected to /dev/null
, so you won't see anything from the application when using docker logs
. Most applications write everything to a log file too. If you do want to see this output with docker logs
, you can set DEBUG
to yes
.