container overlay size increases when a new torrent is added;
[root@ms2 var]# du -Sh /var/lib/docker/overlay2/0c24011afcc11fb3a1f86874a81b59f659ce02fa017ad1ee5603831c2a4d3193/merged/run/s6/services/qbittorrent | sort -rh | head -5
97G /var/lib/docker/overlay2/0c24011afcc11fb3a1f86874a81b59f659ce02fa017ad1ee5603831c2a4d3193/merged/run/s6/services/qbittorrent
12K
Also the incomplete torrent files are created on the correct location
Information
container overlay size increases when a new torrent is added; [root@ms2 var]# du -Sh /var/lib/docker/overlay2/0c24011afcc11fb3a1f86874a81b59f659ce02fa017ad1ee5603831c2a4d3193/merged/run/s6/services/qbittorrent | sort -rh | head -5 97G /var/lib/docker/overlay2/0c24011afcc11fb3a1f86874a81b59f659ce02fa017ad1ee5603831c2a4d3193/merged/run/s6/services/qbittorrent 12K
Also the incomplete torrent files are created on the correct location
Current setup
Docker on CentOS7 host
guillaumedsde/alpine-qbittorrent-openvpn:latest@sha256:2ae14174f55be6a17a7128f2d0352d3b05239a00eaf26b4801691d7b213becda
docker-compose.yml
file ordocker run
commandhow did you start the container? (don't forget to use backticks for creating a proper code block)
Attempted Fix(es)
Download location is set to be on a different drive than /var, and it