Can't see share data from inside docker container

Rock-ons
1

So I’m attempting to mount a share in a pure docker image, via this startup script. Essentially it just starts a docker image with mount points to my main file server share:

docker run -d --user $UID:$GID \
    -p 8080:8080 -p 6881:6881/tcp -p 6881:6881/udp \
    -v /config:/mnt2/Cold/System/QBT \
    -v /torrents:/mnt2/Cold/System/QBT/TorrentFiles \
    -v /downloads:/mnt2/Cold \
    wernight/qbittorrent

And it seems pretty straightforward. I’ve tested this on local directories, and everything works without any kind of issue. But the moment I try and mount something in /mnt2, I can’t see anything in that mount folder from inside the docker container once it’s running. Running a docker inspect on the image gives me this:

    "Mounts": [
        {
            "Type": "bind",
            "Source": "/downloads",
            "Destination": "/mnt2/Cold",
            "Mode": "",
            "RW": true,
            "Propagation": ""
        },
        {
            "Type": "volume",
            "Name": "de2a7a6849c44309c23325ebcda45b3e67e781be5f0b2a07cd64a671b0dbf568",
            "Source": "/mnt2/RockOnShare/volumes/de2a7a6849c44309c23325ebcda45b3e67e781be5f0b2a07cd64a671b0dbf568/_data",
            "Destination": "/config",
            "Driver": "local",
            "Mode": "",
            "RW": true,
            "Propagation": ""
        },
        {
            "Type": "volume",
            "Name": "8341258874b5281463ec531718db9b5963a9533e5742f753c906476580a96e5f",
            "Source": "/mnt2/RockOnShare/volumes/8341258874b5281463ec531718db9b5963a9533e5742f753c906476580a96e5f/_data",
            "Destination": "/downloads",
            "Driver": "local",
            "Mode": "",
            "RW": true,
            "Propagation": ""
        },
        {
            "Type": "volume",
            "Name": "a1c0969cf69a83105af117c9d650ab49525a81dc70fff54c6e595fa08b36a661",
            "Source": "/mnt2/RockOnShare/volumes/a1c0969cf69a83105af117c9d650ab49525a81dc70fff54c6e595fa08b36a661/_data",
            "Destination": "/torrents",
            "Driver": "local",
            "Mode": "",
            "RW": true,
            "Propagation": ""
        },
        {
            "Type": "bind",
            "Source": "/config",
            "Destination": "/mnt2/Cold/System/QBT",
            "Mode": "",
            "RW": true,
            "Propagation": ""
        },
        {
            "Type": "bind",
            "Source": "/torrents",
            "Destination": "/mnt2/Cold/System/QBT/TorrentFiles",
            "Mode": "",
            "RW": true,
            "Propagation": ""
        }
    ],

It’s the strangest thing, and I don’t know where these extra volumes are coming from. Anyone know what I’m doing wrong, and is there anything extra required for a docker image to access a share? I’ve tried darn near everything and I’m at a loss at what to do next.

2

This is user error, can be closed.

3

@overtime Welcome to the Rockstor community.
Thanks for the update, but given others may well run into the same issue; what in the end did:

turn out to be? May well help others that run into the same issue. Ie was it ‘user rights’ or scheduling your script after Rockstor does it’s mount? There are bound to be others on the forum who are also curios.

Cheers.

4

yeah, sure thing.

It was pretty simple, to be honest. I had the source and destination shares backwards.so as soon as I swapped them (see above) everything worked fine.

1 Like