Rclone
uramaki.rclone
Command-line tool for copying, syncing and mounting data across more than 70 cloud and object storage backends, with checksum verification, encryption and bandwidth limits.
A Docker Compose file for Rclone alone, generated from the catalog and checked by the safety inspector. Sign in and use Kitchen Credits to activate it.
Uses the Medusa cart and payment-session path. This test control does not create an order or capture payment.
Rclone treats each configured backend as a remote that can be listed, copied from and synchronised against any other, verifying transfers by checksum and using server-side copy where a provider supports it so data need not pass through the running machine. Beyond transfers it can mount a remote as a filesystem, serve one over HTTP or WebDAV, and encrypt file contents and names transparently so a provider stores only ciphertext. Bandwidth scheduling, transfer concurrency, filtering rules and dry-run mode make it practical for large recurring jobs. A first deployment mounts a persistent configuration file, adds one remote and lists its contents.
You know it worked when
- The binary reports its version and lists the configured remotes.
- Listing a remote returns its actual contents.
- A file copies to the remote and verifies with a matching checksum.
- A dry run of a sync reports the intended changes without making them.
- The configuration file persists across container restarts.
Known sharp edges
- Sync deletes at the destination to match the source, so running it with the two reversed destroys data with no undo — the copy subcommand is the safe default.
- Remote credentials sit in the configuration file, which must be a persistent volume and treated as a secret.
- Transfers to metered providers incur egress and per-request charges that the tool does not report.
- Mounting a remote as a filesystem requires the FUSE device passed into the container, and without it the mount subcommand fails while every other operation works.