readystack/redash repository overview

⁠Redash

readystack/redash:v26.9.0-CE-ubuntu24.04-r3

A cosign-signed build of github.com/getredash/redash v26.9.0 (BSD-2-Clause), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:386580dd2db53e99e27c01730d9df335911138f68ea08a98840b156413f41a60 on 2026-10-27.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products.html#redash⁠
• ReadyStack release check — passed at release on 2026-10-27: 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:386580dd2db53e99e27c01730d9df335911138f68ea08a98840b156413f41a60; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/redash:v26.9.0-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (redash).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v26.9.0-CE-ubuntu24.04-r3 — 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/redash:v26.9.0-CE-ubuntu24.04-r3

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

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

⁠Deployment

ONE product container (supervisord runs the gunicorn web server [:5000] + an RQ worker listening on all six queues + the RQ scheduler) PLUS two required datastore sidecars the customer provides: PostgreSQL and Redis. NOT self-contained. This LEAN CE image ships the MAIN dependency set only: the ~45 optional datasource drivers of upstream's all_ds group (snowflake, cassandra, mysqlclient, pandas, etc.), the GPL-conflicting ldap3 extra, and the proprietary msodbcsql18/Simba ODBC drivers are NOT included — query runners degrade gracefully (a runner is enabled only when its Python driver imports). PostgreSQL/JSON/URL/Prometheus/Elasticsearch/ClickHouse-class runners work out of the box; MySQL and CSV are not available (their drivers, mysqlclient and pandas, are in all_ds), and the Microsoft SQL Server (ODBC) and Databricks types are listed (their Python driver, pyodbc, is installed) but cannot connect, because no ODBC driver is installed.

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 =.

redash-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_PW

redash.env:

# Needed at every start; generate both once and keep them (REDASH_SECRET_KEY encrypts the stored data-source settings).
REDASH_COOKIE_SECRET=YOUR_LONG_RANDOM_SECRET
REDASH_SECRET_KEY=YOUR_OTHER_RANDOM_SECRET
# Needed at every start, with the same password as POSTGRES_PASSWORD.
REDASH_DATABASE_URL=postgresql://redash:YOUR_POSTGRES_PW@db:5432/redash

docker network create redash-net
docker run -d --name db --network redash-net -e POSTGRES_DB=redash -e POSTGRES_USER=redash --env-file ./redash-db.env -v redash-db:/var/lib/postgresql/data postgres:16
docker run -d --name redis --network redash-net redis:7-alpine
docker run -d --name redash --network redash-net -p 5000:5000 -e REDASH_REDIS_URL=redis://redis:6379/0 --env-file ./redash.env readystack/redash:v26.9.0-CE-ubuntu24.04-r3

The three containers share the redash-net network; db is the PostgreSQL container the backup and restore steps name. The database password appears twice, in POSTGRES_PASSWORD in redash-db.env and inside REDASH_DATABASE_URL in redash.env: in the URL, percent-encode characters such as @ : / % # and spaces. Generate REDASH_COOKIE_SECRET and REDASH_SECRET_KEY once and keep them. The first start creates the schema; /ping answers when Redash is up, then open /setup to create your organisation and administrator. The archive ships no Compose file.

⁠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:b3c9ce83782aca3c67fa2946c8d721523e2b78c0906edde5293ced895ea3d4c5 on 2026-10-27.

— ReadyStack · readystack.dev