Self-host Apache Superset with Levelrail
A business intelligence platform for exploring data and building dashboards, with its metadata kept in SQLite.
- Authorapache
- LicenceApache-2.0
- Memory2 GiB
- Archarm64
- Services1
How to self-host Apache Superset
-
Pull the images
One image is pulled on your server.
Show images
apache/superset:4.1.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8088.
-
Fill in the secrets
2 secrets are 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.
Apache Superset requirements
- Memory
- About 2 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8088
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Apache Superset. 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 Apache Superset docs page.
Deploy Apache Superset your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Apache Superset from the CLI
levelrail-cli templates install superset --name my-superset Deploy Apache Superset with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/superset/install \
-d '{
"name": "my-superset"
}' Apache Superset configuration
Apache Superset services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| superset | apache/superset:4.1.1 | 8088 | home -> /app/superset_home |
Apache Superset environment variables
| Variable | Service | Value |
|---|---|---|
| ADMIN_PASSWORD | superset | Generated at deploy |
| ADMIN_USERNAME | superset | Preset by the template |
| SUPERSET_SECRET_KEY | superset | Generated at deploy |
Ports and volumes
- Ports
- 8088
- Volumes
- 1 named mount: home -> /app/superset_home
Apache Superset FAQ
How much memory does Apache Superset need?
The catalog lists about 2 GiB of memory for Apache Superset.
Does Apache Superset run on arm64?
For Apache Superset, an arm64 image is published; amd64 is image published.
What licence is Apache Superset under?
Apache Superset is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Apache Superset need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Apache Superset use?
Apache Superset listens on port 8088 inside the stack.
Where does Apache Superset keep its data?
In a named volume: home mounted at /app/superset_home.
Can I deploy Apache Superset 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 superset for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image apache/superset:4.1.1 is what you deploy there.