readystack/valkey repository overview

⁠Valkey

readystack/valkey:9.1.3-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/valkey-io/valkey 9.1.3 (BSD-3-Clause — the Linux Foundation OSS fork of Redis), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Developers who need a key-value data store for caching, message queues, sessions and other real-time workloads.

Why: Valkey is an open-source key-value datastore and data structure server, used for caching, message queues and as a primary database, with a plugin system for new data structures.

Use case: A web application computes the same expensive results again and again. It stores each result in Valkey under a key with a timeout; later requests read the stored value instead of recomputing it, and Valkey deletes the entries when their timeout expires.

About the upstream project, written from its own description: https://github.com/valkey-io/valkey⁠ · https://valkey.io/⁠ · https://valkey.io/commands/expire/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:9cdcd1a7fff2221634ecd2af9052ebfb302620c2dc30a73ce1644ab108ec7808 on 2026-10-29.

• 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/valkey⁠
• 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:9cdcd1a7fff2221634ecd2af9052ebfb302620c2dc30a73ce1644ab108ec7808; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/valkey:9.1.3-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (valkey).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 9.1.3-CE-ubuntu24.04-r1 — 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.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• 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/valkey:9.1.3-CE-ubuntu24.04-r1

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/valkey:9.1.3-CE-ubuntu24.04-r1 (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 (valkey-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. Drop-in Redis-compatible (RESP protocol, reports redis_version 7.2.4 for client compat).

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 valkey.env with install -m 600 /dev/null valkey.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. Read at every start: the entrypoint turns it into requirepass.
VALKEY_PASSWORD=YOUR_VALKEY_PASSWORD

docker run -d --name valkey -p 6379:6379 --env-file ./valkey.env -v valkey-data:/data readystack/valkey:9.1.3-CE-ubuntu24.04-r1

Keep the VALKEY_PASSWORD line in valkey.env: the entrypoint reads it at every start, and recreating the container without it starts Valkey with no password (tested). Without a password the server still starts but accepts only clients inside the container, e.g. docker exec valkey valkey-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/valkey⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:49b358637959143830713378adf5d20565f3155a8914dcae172f5bb2f52fec7e on 2026-10-27.

— ReadyStack · readystack.dev