readystack/redis repository overview

⁠Redis

readystack/redis:8.10.2-CE-ubuntu24.04-r3

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/redis/recipe⁠
• Upstream source at this release's pinned commit (8.10.2): https://github.com/redis/redis/tree/498ecd0d6d007db11ddb3aea9428552598a78622⁠
• Product page: https://readystack.dev/products/redis⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/redis⁠
• Release history (JSON): https://readystack.dev/api/releases/redis⁠
• Defect record: https://readystack.dev/defects.html?product=redis⁠
• Today's scan: https://readystack.dev/products/redis#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=redis⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/redis/redis 8.10.2 (AGPL-3.0-only, the OSS option of the 8.x RSALv2/SSPLv1/AGPLv3 tri-license), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Developers building applications that need fast access to data: caches, sessions, queues, leaderboards and real-time features.

Why: Redis is an in-memory data store and data structure server: strings, lists, sets, hashes, sorted sets, streams and JSON, with key expiry, pub/sub, and search and vector query features.

Use case: A busy website keeps querying its main database for the same product pages and user sessions. With Redis in front, the site caches page data with an expiry time and stores sessions in memory, so most reads skip the main database and pages return faster.

About the upstream project, written from its own description: https://github.com/redis/redis⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:73afec843813205760e958aba1c7def00fc1fad7a32163243553fa005a6805da 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/redis⁠
• 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:73afec843813205760e958aba1c7def00fc1fad7a32163243553fa005a6805da; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/redis:8.10.2-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (redis).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 8.10.2-CE-ubuntu24.04-r3 — the release listed 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/redis:8.10.2-CE-ubuntu24.04-r3

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/redis:8.10.2-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

Single container, single self-contained C binary (redis-server) compiled from source, foreground process (PID 1). An in-memory key-value data store; state persists to disk as an RDB snapshot (and optionally an AOF) under /data. NO relational/SQL database, NO external datastore, NO sidecar. The image IS the complete running instance (no docker-compose, no cluster).

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create redis.env with install -m 600 /dev/null redis.env, then write these 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 =.

# The password every client needs. Docker passes this env file's lines at every start, and the entrypoint turns REDIS_PASSWORD into requirepass.
REDIS_PASSWORD=YOUR_REDIS_PASSWORD

docker run -d --name redis -p 6379:6379 --env-file ./redis.env -v redis-data:/data readystack/redis:8.10.2-CE-ubuntu24.04-r3

Keep the REDIS_PASSWORD line in redis.env: the entrypoint reads it at every start, and recreating the container without it starts Redis with no password, accepting only clients inside the container (tested). Without a password the server still starts but accepts only clients inside the container, e.g. docker exec redis redis-cli PING.

⁠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 a free download for any registered account at readystack.dev/products/redis⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:05497f9a42527131301397a1a760fc62d443eceafa86a10b0a15dfe890d29b90 on 2026-10-27.

— ReadyStack · readystack.dev