Table of Contents
Docker Installation
A simple Dockerfile is available in this repo if you'd like to build it yourself.
The official build on github is available here:
docker run -it -v <PATH_TO_CONFIG>:/config:rw ghcr.io/stuffanthings/qbit_manage:latest
-
The -v <PATH_TO_CONFIG>:/config:rw mounts the location you choose as a persistent volume to store your files.
- Change <PATH_TO_CONFIG> to a folder where your config.yml and other files are.
- The docker image defaults to running the config named config.yml in your persistent volume.
- Use quotes around the whole thing if your path has spaces i.e. -v "<PATH_TO_CONFIG>:/config:rw"
-
Fill out your location for your downloads downloads folder (
Root_Dir
).- qbit_manage needs to be able to view all torrents the way that your qbittorrent views them.
- Example: If you have qbittorrent mapped to
/mnt/user/data/:/data
This means that you MUST have qbit_managed mapped the same way. - Furthermore, the config file must map the root directory you wish to monitor. This means that in our example of
/data
(which is how qbittorrent views the torrents) that if in your/data
directory you drill down to/torrents
that you'll need to update your config file to/data/torrents
- Example: If you have qbittorrent mapped to
- This could be different depending on your specific setup.
- The key takeaways are
- Both qbit_manage needs to have the same mappings as qbittorrent
- The config file needs to drill down (if required) further to the desired root dir.
- qbit_manage needs to be able to view all torrents the way that your qbittorrent views them.
-
remote_dir
: is not required and can be commented out with#
Please see Commands for a list of arguments and docker environment variables.
Here is an example of a docker compose
version: "3.7"
services:
qbit_manage:
container_name: qbit_manage
image: ghcr.io/stuffanthings/qbit_manage:latest
volumes:
- /mnt/user/appdata/qbit_manage/:/config:rw
- /mnt/user/data/torrents/:/data/torrents:rw
- /mnt/user/appdata/qbittorrent/:/qbittorrent/:ro
environment:
- QBT_RUN=false
- QBT_SCHEDULE=1440
- QBT_CONFIG=config.yml
- QBT_LOGFILE=activity.log
- QBT_CROSS_SEED=false
- QBT_RECHECK=false
- QBT_CAT_UPDATE=false
- QBT_TAG_UPDATE=false
- QBT_REM_UNREGISTERED=false
- QBT_REM_ORPHANED=false
- QBT_TAG_TRACKER_ERROR=false
- QBT_TAG_NOHARDLINKS=false
- QBT_SHARE_LIMITS=false
- QBT_SKIP_CLEANUP=false
- QBT_DRY_RUN=false
- QBT_LOG_LEVEL=INFO
- QBT_DIVIDER==
- QBT_WIDTH=100
restart: on-failure:2
You will also need to define not just the config volume but the volume to your torrents, this is in order to use the recycling bin, remove orphans and the no hard link options
Here we have /mnt/user/data/torrents/
mapped to /data/torrents/
furthermore in the config file associated with it the root_dir is mapped to /data/torrents/
We also have /mnt/user/appdata/qbittorrent/
mapped to /qbittorrent
and in the config file we associated torrents_dir to /qbittorrent/data/BT_backup
to use the save_torrents functionality