Self-host SeaweedFS with Levelrail
A distributed file and object store with an S3 gateway, built for billions of small files.
- Authorseaweedfs
- LicenceApache-2.0
- Memory1 GiB
- Archarm64
- Services2
How to self-host SeaweedFS
-
Pull the images
2 images are pulled on your server.
Show images
chrislusf/seaweedfs:3.99chrislusf/seaweedfs:3.99
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on ports 8333, 9333, 8888.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 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.
SeaweedFS requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8333, 9333, 8888
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes ports 8333, 9333, 8888 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then SeaweedFS. 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 SeaweedFS docs page.
Deploy SeaweedFS your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy SeaweedFS from the CLI
levelrail-cli templates deploy seaweedfs --name my-seaweedfs Deploy SeaweedFS with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/seaweedfs/deploy SeaweedFS configuration
SeaweedFS services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| s3 | chrislusf/seaweedfs:3.99 | 8333 | none |
| seaweedfs | chrislusf/seaweedfs:3.99 | 9333, 8888 | seaweedfs_data -> /data |
SeaweedFS environment variables
| Variable | Service | Value |
|---|---|---|
| S3_ACCESS_KEY | s3 | Generated at deploy |
| S3_SECRET_KEY | s3 | Generated at deploy |
Ports and volumes
- Ports
- 8333, 9333, 8888
- Volumes
- 1 named mount: seaweedfs_data -> /data
SeaweedFS FAQ
How much memory does SeaweedFS need?
The catalog lists about 1 GiB of memory for SeaweedFS across its 2 services.
Does SeaweedFS run on arm64?
For SeaweedFS, an arm64 image is published; amd64 is image published.
What licence is SeaweedFS under?
SeaweedFS is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does SeaweedFS need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does SeaweedFS use?
SeaweedFS listens on ports 8333, 9333 and 8888 inside the stack.
Where does SeaweedFS keep its data?
In a named volume: seaweedfs_data mounted at /data.
Can I deploy SeaweedFS 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 seaweedfs for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image chrislusf/seaweedfs:3.99, chrislusf/seaweedfs:3.99 is what you deploy there.