storage_path is ignored

[RyanGuyCode]

I find that the path that is required for data is completely ignored once running. input this: -v /your/storage/path/:/data \ actual location: mv5:/var/lib/docker/volumes/804502e081c60b68ad8a43d742a53d1822ddece7ce98876064e5e0e15cbd37bf/_data/qBittorrent/downloads#

version: '2'
services:
    qbittorrent-openvpn:
        volumes:
            - '/srv/dev-disk-by-label-General3/shareA/Downloads/:/data'
            - '/etc/localtime:/etc/localtime:ro'
        environment:
            - CREATE_TUN_DEVICE=true
            - OPENVPN_PROVIDER=NORDVPN
            - OPENVPN_USERNAME=username
            - OPENVPN_PASSWORD=password
            - WEBPROXY_ENABLED=false
            - LOCAL_NETWORK=192.168.29.0/24
            - HEALTH_CHECK_HOST=google.com
        logging:
            driver:
                - json-file
            options:
                max-size: 10m
        ports:
            - '8080:8080'
        devices:
            - /dev/net/tun:/dev/net/tun
        cap_add:
            - NET_ADMIN
        image: guillaumedsde/qbittorrent-openvpn

Logs

Sat Mar 28 09:44:20 2020 VERIFY EKU OK,
Sat Mar 28 09:44:20 2020 Validating certificate extended key usage,
Sat Mar 28 09:44:20 2020 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA,
Sat Mar 28 08:44:20 2020 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key,
Sat Mar 28 08:44:20 2020 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key,
Sat Mar 28 08:44:20 2020 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA,
Sat Mar 28 09:44:20 2020 TLS: tls_process: killed expiring key,
Sat Mar 28 09:44:20 2020 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA,
Sat Mar 28 09:44:20 2020 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA4,
Sat Mar 28 09:44:20 2020 VERIFY KU OK,
Sat Mar 28 09:44:20 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication,
Sat Mar 28 09:44:20 2020 VERIFY OK: depth=0, CN=us3558.nordvpn.com,
Sat Mar 28 09:44:20 2020 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key,
Sat Mar 28 09:44:20 2020 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key,
Sat Mar 28 08:44:20 2020 VERIFY OK: depth=0, CN=us3558.nordvpn.com,
Sat Mar 28 08:44:20 2020 VERIFY EKU OK,
Sat Mar 28 08:44:20 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication,
Sat Mar 28 08:44:20 2020 Validating certificate extended key usage

Host system: 5:19.03.8~3-0~debian-buster Running on an openmediavault host.

[johnmcba]

At least in my case, it did mount the location in the docker i just had to change the path in qbittorrent from /config/ to /data/. Hope this helps.

[guillaumedsde]

@johnmcba's fix works, otherwise, I've set the default download directory to /data in 72c42dc7b42c25eb411d5a731b8efb20ccc5ecdb if you pull the image again once its built, this should be fixed, feel free to reopen if that did not fix it :)

[RyanGuyCode]

The thing that doesn't make sense, is that the path that I created in my composer file is not used at all. Rather, it goes into the following directory. That makes no sense at all. If I change to the directory in qbit that I posted, I literally see nothing anywhere. Note: I am a noob at this, but its not the first I've deployed. I feel like I should be adding a config path. /var/lib/docker/volumes/485aa46fe4818ee8d564422afb2a392acd39c34ba74760e482f9b6d946e4e260/_data/qBittorrent/downloads

[johnmcba]

well going by your compose file in the first post that would mean that /srv/dev-disk-by-label-General3/shareA/Downloads/ = /data/ in the qbit.

so assuming you want Downloads to be the folder that the downloads from qbit go that would make the qbit download directory /data/. Making sure to use the / at the end of data.

If your getting them in the docker config directory then it must be mounting that directory in the docker.

and just for another example ill show you mine, I dont use compose so mine is just a run command i run in a terminal: docker run --cap-add=NET_ADMIN -d
-v /mnt/Seagate/downloads/:/data
-v /etc/localtime:/etc/localtime:ro
--env-file /home/john/Documents/dockerenv
-e CREATE_TUN_DEVICE=true
-e OPENVPN_PROVIDER=WINDSCRIBE
-e OPENVPN_CONFIG=US-East-udp
-e OPENVPN_USERNAME=username
-e OPENVPN_PASSWORD=password
-e WEBPROXY_ENABLED=false
-e LOCAL_NETWORK=192.168.0.0/16
--log-driver json-file
--log-opt max-size=10m
-p 8080:8080
--restart=always
guillaumedsde/qbittorrent-openvpn So for mine you can see i mount my drive at /mnt/Seagate/downloads/ then inside that folder i have a completed folder i download to. So my qbit directory is /data/completed/.

[RyanGuyCode]

@johnmcba I follow you 100% I've played with it a number of times, but it never goes to my volume. rather, it always goes to the /var/lib/docker/volumes/kdkd/_data/qBittorrent directory, along with the config, data, downloads folder. Its as if I never added that volume. This doesn't happen with any other docker I deploy.

[johnmcba]

The only other thing I can think of is it's a permissions thing. Maybe try running the docker as root and see if it mounts/downloads to that folder then. I'm no linux/docker pro by any means, but that's the only other thing I can think of.

[guillaumedsde]

(the issue reference above is incorrect) @RyanGuyCode have you tried starting the container with a fresh qbittorrent config? (remove the config directory on your host (this wil unlink all your torrents from qbittorrent if you have downloaded any and start again)

[RyanGuyCode]

@guillaumedsde Yes, I do run as root. I'll try again that way.

[guillaumedsde]

Hi @RyanGuyCode I've also updated the README.md with a fix that might be of interest for fixing this: more details in https://github.com/guillaumedsde/docker-qbittorrent-openvpn/issues/6

[RyanGuyCode]

Excellent! Will review.

Regards, Ryan Milton On May 25, 2020, 4:01 PM -0500, guillaumedsde [email protected], wrote:

Hi @RyanGuyCodehttps://github.com/RyanGuyCode I've also updated the README.md with a fix that might be of interest for fixing this: more details in #6https://github.com/guillaumedsde/docker-qbittorrent-openvpn/issues/6

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/guillaumedsde/docker-qbittorrent-openvpn/issues/1#issuecomment-633715037, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFP52SZZWG3HWO5RST6HVF3RTLMBPANCNFSM4LVTFJ5Q.