Self-host RustFS with Levelrail
VerifiedAn S3-compatible object storage server written in Rust, with a web console. One container serves the S3 API on port 9000 and the console on port 9001. Access and secret keys are generated at install time.
- Authorrustfs
- LicenceApache-2.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host RustFS
-
Pull the images
One image is pulled on your server.
Show images
rustfs/rustfs:1.0.4
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 9001, 9000.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 3 settings are 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 to the console with the access key and secret key from the service environment settings.
RustFS requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 9001, 9000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Verified. Verified on arm64 with image tag 1.0.4. Our CI ran this exact image version and it answered on its health path. Evidence
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then RustFS. 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 RustFS docs page.
Deploy RustFS your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy RustFS from the CLI
levelrail-cli templates deploy rustfs --name my-rustfs Deploy RustFS with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/rustfs/deploy RustFS configuration
RustFS services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| rustfs | rustfs/rustfs:1.0.4 | 9001, 9000 | data -> /data |
RustFS environment variables
| Variable | Service | Value |
|---|---|---|
| RUSTFS_ACCESS_KEY | rustfs | Generated at deploy |
| RUSTFS_ADDRESS | rustfs | Preset by the template |
| RUSTFS_CONSOLE_ADDRESS | rustfs | Preset by the template |
| RUSTFS_CONSOLE_ENABLE | rustfs | Preset by the template |
| RUSTFS_SECRET_KEY | rustfs | Generated at deploy |
Ports and volumes
- Ports
- 9001, 9000
- Volumes
- 1 named mount: data -> /data
RustFS FAQ
How much memory does RustFS need?
The catalog lists about 256 MiB of memory for RustFS.
Does RustFS run on arm64?
For RustFS, arm64 is tested; amd64 is image published.
What licence is RustFS under?
RustFS is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does RustFS need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does RustFS use?
RustFS listens on ports 9001 and 9000 inside the stack.
Where does RustFS keep its data?
In a named volume: data mounted at /data.
Can I deploy RustFS on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id rustfs for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image rustfs/rustfs:1.0.4 is what you deploy there.