hotio/rclone
GitHub
docker.io
/ ghcr.io
/ quay.io
Rclone
00
Starting the container¶
docker run --rm cr.hotio.dev/hotio/rclone ...
The default ENTRYPOINT is rclone.
Tags¶
Where can I find the source of the image?
You can click the tag name to go to the source on GitHub for that particular tag. Every tag has its own branch.
The master branch is used as a landing page and to store some statistics used by this page to populate the table.
Temporary tags/branches might not show up in the table, but are also generally not for end-user consumption.
Clicking the commit sha brings you to the exact source of that commit.
| Tag | Upstream | Version | Commit | Last Updated |
|---|
Using a rclone mount on the host¶
By setting the bind-propagation to shared on the volume mountpoint, like this -v /data/mountpoint:/mountpoint:shared, you are able to access the mount from the host. If you want to use this mount in another container, the best solution is to create a volume on the parent folder of that mount with bind-propagation set to slave. For example, -v /data:/data:slave (/data on the host, would contain the previously created volume mountpoint). Doing it like this will ensure that when the container creating the mount restarts, the other containers using that mount will recover and keep working.
Extra docker privileges¶
In most cases you will need some or all of the following flags added to your command to get the required docker privileges when using rclone mount.
--security-opt apparmor:unconfined --cap-add SYS_ADMIN --device /dev/fuse