readystack/superset repository overview

⁠Apache Superset

readystack/superset:6.1.0-CE-ubuntu24.04-r2

A cosign-signed build of github.com/apache/superset 6.1.0 (Apache-2.0), built clean-room from upstream's published release artifact by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:dc60aabd43c350b04cfb73941a764feed202728a74a23bc8c65e0d89708647b8 on 2026-10-24.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with ce.rodeo's published rubric) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products.html#superset⁠
• ReadyStack release check — passed at release on 2026-10-24: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:dc60aabd43c350b04cfb73941a764feed202728a74a23bc8c65e0d89708647b8; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/superset:6.1.0-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (superset).
• Built from upstream's published release artifact (https://pypi.org/project/apache-superset/6.1.0/⁠) by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 6.1.0-CE-ubuntu24.04-r2 — the release on sale at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/superset:6.1.0-CE-ubuntu24.04-r2

# ✗ unsupported (do not pull)
docker pull readystack/superset:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/superset:6.1.0-CE-ubuntu24.04-r2 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

ONE container running Superset's web server (gunicorn, non-root user superset, port 8088) PLUS a PostgreSQL database you provide for Superset's own metadata (users, dashboards, charts, saved queries). The image has no database server, no Redis and no Celery worker: caching is off (NullCache) and async queries, alerts, reports and thumbnails stay disabled unless you add Redis and a worker yourself. Every start runs superset db upgrade and superset init before the server listens.

Secrets go in env files that only you can read, not on the command line, and passwords that only set up the first start come out of them after setup. Create each file with install -m 600 /dev/null <file>, then write its lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

superset-db.env:

# First start only: the postgres image reads POSTGRES_PASSWORD only when it initialises its empty volume. You can remove this line after the first start and recreate the db container; the database keeps the password.
POSTGRES_PASSWORD=YOUR_POSTGRES_PASSWORD

superset.env:

# Needed at every start (the container exits without it); keep it unchanged.
SUPERSET_SECRET_KEY=YOUR_SECRET_KEY
# Needed at every start: the metadata database, with the same password as POSTGRES_PASSWORD.
SUPERSET_DATABASE_URI=postgresql+psycopg2://superset:YOUR_POSTGRES_PASSWORD@db:5432/superset
# First start only: the start that creates the admin (SUPERSET_ADMIN_USERNAME) gives it SUPERSET_ADMIN_PASSWORD. Remove this line after setup and recreate the container; the admin keeps the password.
SUPERSET_ADMIN_PASSWORD=YOUR_ADMIN_PASSWORD

docker network create superset-net
docker run -d --name db --network superset-net -e POSTGRES_DB=superset -e POSTGRES_USER=superset --env-file ./superset-db.env -v superset-db:/var/lib/postgresql/data postgres:16
docker run -d --name superset --network superset-net -p 8088:8088 -e SUPERSET_ADMIN_USERNAME=admin --env-file ./superset.env -v superset-home:/var/lib/superset readystack/superset:6.1.0-CE-ubuntu24.04-r2

Use the same database password for POSTGRES_PASSWORD in superset-db.env and inside SUPERSET_DATABASE_URI in superset.env (in the URL, percent-encode characters such as @ : / % # and spaces). The first start migrates the metadata database and creates the admin (SUPERSET_ADMIN_USERNAME, default admin) with SUPERSET_ADMIN_PASSWORD; /health answers OK afterwards. Then remove the SUPERSET_ADMIN_PASSWORD line from superset.env and recreate the container on the same volume (docker rm -f superset, then its docker run line again): the admin keeps its password, which is then no longer in the container's environment (tested).

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:fbff7aa3acdfbb59c15f8b4068157e3d670e8371368693ddb9dbfe584c9f100f on 2026-10-24.

— ReadyStack · readystack.dev