Self-host rclone with Levelrail
The rclone remote control web GUI for managing and syncing files across dozens of cloud storage providers.
- Authorrclone
- LicenceMIT
- Memory256 MiB
- Services1
How to self-host rclone
-
Pull the images
One image is pulled on your server.
Show images
rclone/rclone:1.76.0
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 5572.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Sign in as admin with the generated password, then add your remotes.
rclone requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 5572
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then rclone. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the rclone docs page.
Deploy rclone your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy rclone from the CLI
levelrail-cli templates install rclone --name my-rclone Deploy rclone with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/rclone/install \
-d '{
"name": "my-rclone"
}' rclone configuration
rclone services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| rclone | rclone/rclone:1.76.0 | 5572 | config -> /config/rclonedata -> /data |
rclone environment variables
| Variable | Service | Value |
|---|---|---|
| RCLONE_RC_PASS | rclone | Generated at deploy |
| RCLONE_RC_USER | rclone | Preset by the template |
Ports and volumes
- Ports
- 5572
- Volumes
- 2 named mounts: config -> /config/rclone, data -> /data
rclone FAQ
How much memory does rclone need?
The catalog lists about 256 MiB of memory for rclone.
Does rclone run on arm64?
For rclone, arm64 support is not confirmed; amd64 is unknown.
What licence is rclone under?
rclone is licensed under MIT, which is permissive, with few conditions on reuse.
Does rclone need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does rclone use?
rclone listens on port 5572 inside the stack.
Where does rclone keep its data?
In named volumes: config mounted at /config/rclone and data mounted at /data.
Can I deploy rclone on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for rclone, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image rclone/rclone:1.76.0 is what you deploy there.