readystack/redash repository overview

⁠Redash

readystack/redash:v26.3.0-CE-trixie-r1

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

⁠What you get

• Docker Scout — re-checked daily; today's grade and the reason for it are at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key; verify with cosign verify --key https://readystack.dev/keys/cosign.pub --insecure-ignore-tlog=true readystack/redash:v26.3.0-CE-trixie-r1.
• Built from source, non-root.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v26.3.0-CE-trixie-r1 — the release on sale at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is hermetically built, signed, attested, and supported under your 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 patched or re-graded: move to the current release. A superseded release's build kit is available through 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.3.0-CE-trixie-r1

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

Each release tag is signed; verify with cosign verify --key https://readystack.dev/keys/cosign.pub --insecure-ignore-tlog=true readystack/redash:v26.3.0-CE-trixie-r1 (ReadyStack keeps signatures off the public transparency log, so the check is key-only). Support: [email protected]⁠.

⁠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 (all_ds: snowflake/pandas/cassandra/mssql-ODBC/etc), the GPL-conflicting ldap3 extra, and the proprietary msodbcsql18/Simba ODBC blobs are NOT included — query runners degrade gracefully (a runner is enabled only when its driver imports). Postgres/MySQL-via-HTTP/JSON/CSV/URL/Prometheus/Elasticsearch/ClickHouse-class runners work out of the box.

docker network create redash-net
docker run -d --name db --network redash-net -e POSTGRES_DB=redash -e POSTGRES_USER=redash -e 'POSTGRES_PASSWORD=YOUR_POSTGRES_PW' -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_COOKIE_SECRET=YOUR_LONG_RANDOM_SECRET' -e 'REDASH_SECRET_KEY=YOUR_OTHER_RANDOM_SECRET' -e 'REDASH_DATABASE_URL=postgresql://redash:YOUR_POSTGRES_PW@db:5432/redash' -e REDASH_REDIS_URL=redis://redis:6379/0 readystack/redash:v26.3.0-CE-trixie-r1

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 and inside REDASH_DATABASE_URL: in the URL, percent-encode characters such as @ : / % # and spaces. Keep each -e value in single quotes. 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 Agent-ready Archive

The complete --network=none build kit to recreate this exact image yourself — plus admin/DB/API handbooks, seed data, a validated test suite, and signed provenance — is at readystack.dev/buy.html⁠.

— ReadyStack · readystack.dev