readystack/temporal repository overview

⁠Temporal

readystack/temporal:v1.32.1-CE-ubuntu24.04-r3

A cosign-signed build of github.com/temporalio/temporal v1.32.1 (MIT), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

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

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.32.1-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/temporal:v1.32.1-CE-ubuntu24.04-r3

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/temporal:v1.32.1-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 running the temporal-server binary in the foreground, with all four services (frontend, history, matching, worker) in one process and a self-contained pure-Go SQLite store. This is a durable-execution backend, not an application with a UI — clients connect with a Temporal SDK over gRPC on 7233 and run workflows against it.

docker run -d --name temporal -p 127.0.0.1:7233:7233 -p 127.0.0.1:7243:7243 -v temporal-data:/var/lib/temporal readystack/temporal:v1.32.1-CE-ubuntu24.04-r3

Publishes the frontend ports on 127.0.0.1 only: authorization is off by default, so anything that can reach 7233 or 7243 has full control of every namespace and workflow (see Access control and passwords in the handbooks). To serve workers or clients on other hosts, publish the ports on a private network address instead, or turn on JWT authorization first (see Turning on authorization (JWT) in the handbooks). GET http://127.0.0.1:7243/api/v1/namespaces⁠ answers 200 once the server is up. 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:4ef64bf87564b8aabd6a3d5fdbbbe0c122a7edbf9e39bc97c303d0f92fe73034 on 2026-10-27.

— ReadyStack · readystack.dev