thomast_88

I don't have time to write a step-by-step guide today, but later some week I can do one. This thread (including the FAQ) should get you up and running pretty fast though. Any issues you are facing right now?

@jude Do you have Community Applications installed? If not, I suggest you use that. Just search rclone and it will pop up. EDIT: you should add https://github.com/tynor88/docker-templates/tree/master/tynor88

@MTA99 I see :-) But your point is good. The application can as well fail fast, as the rclone mount feature requires the colon to be there. Interesting. How many folder / files were in the directory you tried to list?

Right, gotta fix that. I was using a folder which was created by @Waseh's plugin, so my permissions were ok. Yes, i tried to make that clear in two places. (See screenshot). But you're right - it wouldn't work without a colon. I could perhaps check the variable at startup, and fail fast if there is no ":" specified. @MTA99 What do you mean by testing with a small sub folder? It shouldn't take any time to mount. I'm mounting 5 TB encrypted data in no time.

Good catch. I updated the template.

Sure, I'd be happy to receive some feedback on this once you get it up and running.

This plugin spawned from my initial docker which didn't support sharing the rclone FUSE mount. With Rclone-mount it's now possible. I'm not trying to hijack this thread, just want to let people know that I've created a Docker, which can expose the FUSE mount to the host and other docker containers, for those people who prefer dockerizing.

@bobbintb / @hackztor I've created a seperate docker which now supports sharing the FUSE mount to the host and other docker containers: Rclone-mount

Best mount settings for Cloud Services Amazon Cloud Drive: --read-only --buffer-size=1G --max-read-ahead=200M --acd-templink-threshold=0 --dir-cache-time=60m --timeout=30s --contimeout=15s --retries=3 --low-level-retries=1 --stats=0 -v

FAQ Can I use my encrypted ACD/GDrive content with Plex and other dockers? Yes, that's exactly the purpose of this container. Can i haz unlimited space on my unRAID setup? I think 233 TB is the maximum I've seen so far with Amazon Cloud Drive. How do i create the .rclone.conf file? docker exec -it Rclone-mount rclone --config="/config/.rclone.conf" config I already have a .rclone.conf file from the rclone plugin, can I use it rather than creating a new one? Sure, there are two ways: Mount the /config volume so it points to the directory which contains the .rclone.conf file. E.g.: -v "/boot/config/plugins/rclone-beta/":"/config":rw Copy it to: "/mnt/cache/appdata/rclone-mount/config/" I cannot see my mounted volume/files outside of the container Make sure you have this in extra parameters (advanced view): --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfine -v /mnt/disks/rclone_volume/:/data:shared Make sure that this docker container is started before the container you are sharing the volume with. Can i use the copy/sync features of rclone with this docker? Use the other docker i made which supports that. What are the best mount settings for Plex playback / transcoding? See this post And this discussion on the official rclone forum And ajkis wiki on GitHub I want more verbose logging, so I can see what's going on This is not entirely documented yet by rclone, but there is some discussion here. Summarized, in the RCLONE_MOUNT_OPTIONS variable put: -v flag for information logging Or -vv for alot verbose logging Why should I specify the /data mount in the Extra Parameters? Because the unRAID docker GUI does not support the shared mount propagation options, which is required for the rclone FUSE mount to be shared with other containers. I've already opened a feature request to have this option available in the GUI. This option has been added to the GUI by @bonienl and is no longer necessary. Can I change the volume mapping of the mount from /mnt/disks/rclone_volume/ to another location? Yes, in the Extra Parameters change the default value of -v /mnt/disks/rclone_volume/:/data:shared to -v <location>:/data:shared

Docker for Rclone FUSE mount feature (exposable to host and other docker containers, e.g. Plex, Nextcloud, glFTPd) Application Name: Rclone-mount Application Site: http://rclone.org/ Docker Hub: https://hub.docker.com/r/tynor88/rclone-mount/ Docker Store: https://store.docker.com/community/images/tynor88/rclone-mount Github: https://github.com/tynor88/docker-rclone-mount unRAID Template: https://github.com/tynor88/docker-templates/tree/master/tynor88 Setup/Configuration: https://rclone.org/commands/rclone_mount/ Supported Cloud Services: Google Drive Amazon S3 Openstack Swift / Rackspace cloud files / Memset Memstore Dropbox Google Cloud Storage Amazon Drive Microsoft One Drive Hubic Backblaze B2 Yandex Disk The local filesystem Creating the initial config file (.rclone.conf) docker exec -it Rclone-mount rclone --config="/config/.rclone.conf" config IMPORTANT Extra Parameters: In order for the FUSE mount to be exposable to the host and other docker containers, these settings have to be in the Extra Parameters option in the "Advanced View" when setting up the Docker. I've already made them default in the CA template file. --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfine -v /mnt/disks/rclone_volume/:/data:shared With the above settings, the FUSE will be mounted to /mnt/disks/rclone_volume Note if you cannot see the mount inside other dockers This container must be started BEFORE other docker containers when sharing the FUSE mount. For automaticly fixing this at startup, use the great CA Docker Autostart Manager Plugin by @Squid Feel free to post any questions/issues/requests relating to this docker in this thread.

When mounting volumes in docker, we're missing some propagation options ("Access Mode") for the mounted volumes. They are not well documented on the official docker documentation, but some more information can be found here. Currently we can do: RW, RW/Slave, RO, RO/Slave Default is private, we can specify slave but we're missing the "shared" option so we can do -v /mnt/disks/acd_volume/:/data:shared Current work around is just to use the "Extra Parameters". Here some more information regarding the propagation options (c/p from manpages): By default bind mounted volumes are private. That means any mounts done inside container will not be visible on host and vice-a-versa. One can change this behavior by specifying a volume mount propagation property. Making a volume shared mounts done under that volume inside container will be visible on host and vice-a-versa. Making a volume slave enables only one way mount propagation and that is mounts done on host under that volume will be visible inside container but not the other way around. To control mount propagation property of volume one can use :[r]shared, :[r]slave or :[r]private propagation flag. Propagation property can be specified only for bind mounted volumes and not for internal volumes or named volumes. For mount propagation to work source mount point (mount point where source dir is mounted on) has to have right propagation properties. For shared volumes, source mount point has to be shared. And for slave volumes, source mount has to be either shared or slave. Use df <source-dir> to figure out the source mount and then use findmnt -o TARGET,PROPAGATION <source-mount-dir> to figure out propagation properties of source mount. If findmnt utility is not available, then one can look at mount entry for source mount point in /proc/self/mountinfo. Look at optional fields and see if any propagaion properties are specified. shared:X means mount is shared, master:X means mount is slave and if nothing is there that means mount is private.

Ok i tried it myself and it works. The latest image with the dev tag now supports mounting the rclone FUSE mounts back to the host and thereby usable by other containers (e.g. Plex). I created a seperate docker for this: Rclone-mount

Someone managed to mount rclone FUSE mounts to the host properly it seems. Anyone tried this: https://hub.docker.com/r/mumiehub/rclone-mount/ ?

I'm getting this error when using "iotop". I tried reinstalling multiple times already How to fix this?

That's obviously a mistake. I will fix that asap.

I have this problem already since 6.3.0-rc5 . It's easy for me to replicate it. If i start writing new files to the cache array (which is 2x 250 gb evos BTRFS raid 1) server load keeps growing until 50-60, then eventually VM's starts dying, then docker apps. If I stop writing to the cache array then load goes down again to normal (< 1). I noticed the problem when using FileBot Docker container to rename (move) files from cache array -> cache array. First 3-4 files are blazing fast, and then the load just keeps growing. Should i provide some logs, while I'm doing the renaming to further investigate this?

As mentioned earlier it works fine. There is no template for it, but you can still install it from the Community Applications.

docker exec -it Netdata /bin/bash cd /usr/libexec/netdata/plugins.d/

@vurt Great it worked out - and thanks for posting the solution. I will consider changing the default permission of the /data path to RW.

Well, yeah. Crypt is a feature of rclone. It has nothing to do with docker. All docker does is package the program in a container. The docker version might use an older version of rclone before the crypt feature was added, if that's what you are asking. The only real difference between the docker and the plugin versions of rclone, as far as usage goes, is that because of the way docker works you cannot share a mount with another docker. So for instance, if you are planning on using a rclone docker encrypted mount with Plex, you will need the rclone plugin. Yes, i've uploaded several TB's of encrypted data with the docker. However I'm using the plugin for mounting the crypted volume back to my server. So the docker can be used in collaboration with the plugin if you which to use the encrypted volumes in other docker containers like Plex for instace.

You are trying to proxy to sickrage?

I've added Duo Security for Two-Factor Authentication when using this container. They have a free user tier which allows < 10 users. It will basically send a push request / sms to your mobile phone as an extra confirmation when logging in from the Web Interface (for those who have this exposed to the internet). I've followed the steps described here https://duo.com/docs/openvpn and modified them a bit. [*]download and edit duo_openvpn_as.py with secret key etc as described in the link [*]move duo_openvpn_as.py to /mnt/cache/appdata/openvpn-as/scripts [*]docker exec -it openvpn-as /bin/bash [*]chmod a+x /config/scripts/duo_openvpn_as.py [*]/config/scripts/sacli -a <admin_user> -k auth.module.post_auth_script --value_file=/config/scripts/duo_openvpn_as.py ConfigPut [*]/config/scripts/sacli -a <admin_user> Reset [*]Restart the container Now you have 2FA for logins. Write "push", "sms", "phone" and click connect, and you will receive a 2FA.

Why not just create a new user which is admin, and delete the default admin user? Is it recreated upon updates of this container, or did i miss something?

Did you ever figure this out? By reading http://rclone.org/commands/rclone_sync/ it seems like it should be possible? Did you perhaps try to use copy rather than sync?