readystack/etcd repository overview

⁠etcd

readystack/etcd:v3.7.3-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/etcd/recipe⁠
• Upstream source at this release's pinned commit (v3.7.3): https://github.com/etcd-io/etcd/tree/0a173d0410a96d01091b484daae81365bbcde57e⁠
• Product page: https://readystack.dev/products/etcd⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/etcd⁠
• Release history (JSON): https://readystack.dev/api/releases/etcd⁠
• Defect record: https://readystack.dev/defects.html?product=etcd⁠
• Today's scan: https://readystack.dev/products/etcd#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=etcd⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠
• Part of the Kubernetes VM Stack: https://readystack.dev/stacks/kubernetes-vm-stack⁠

A cosign-signed build of github.com/etcd-io/etcd v3.7.3 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Platform engineers who run Kubernetes control planes, and developers of distributed systems that need consistent shared state.

Why: etcd is a distributed, reliable key-value store for a distributed system's most critical data. It replicates writes across its members with the Raft consensus algorithm, so the data stays consistent when a member fails.

Use case: A Kubernetes control plane keeps all of its API data in etcd. Running etcd as a cluster of members on separate machines means the cluster's state survives the loss of one machine, and the remaining members keep serving reads and writes.

About the upstream project, written from its own description: https://github.com/etcd-io/etcd⁠ · https://kubernetes.io/docs/concepts/overview/components/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:b86345e29e39a9d41a26af8d79b9e784c26fb9c6b4614340e6ce663f12fe8f1b 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/etcd⁠
• 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:b86345e29e39a9d41a26af8d79b9e784c26fb9c6b4614340e6ce663f12fe8f1b; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/etcd:v3.7.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 (etcd).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v3.7.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.

• 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/etcd:v3.7.3-CE-ubuntu24.04-r1

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

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

A single container running a single-member etcd cluster as the non-root etcd user (uid 999). etcd is its own datastore: an embedded bbolt key-value store under /data (the --data-dir), so there is no separate database, sidecar or web UI. The image contains three static Go binaries: etcd (the server), etcdctl (the client) and etcdutl (offline data tools).

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 etcd.env with install -m 600 /dev/null etcd.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 =.

# Root's password. The first start of an empty /data creates root with it; later starts ignore it, but keep it here: the documented docker exec etcdctl commands read it from the container's environment.
ETCD_ROOT_PASSWORD=YOUR_STRONG_PASSWORD

docker run -d --name etcd -p 2379:2379 --env-file ./etcd.env -v etcd-data:/data readystack/etcd:v3.7.3-CE-ubuntu24.04-r1

The first start of an empty /data creates the user root with ETCD_ROOT_PASSWORD from etcd.env and turns authentication on. Keep the line in etcd.env afterwards: later starts ignore it, but the documented backup, password and auth commands (docker exec etcd sh -c 'etcdctl --user root --password "$ETCD_ROOT_PASSWORD" ...') read it from the container's environment.

⁠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/etcd⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:b21b8089f1957b35bfaf54647f871c1e9e56d36d20af32a2fdb9b2b6483d62f6 on 2026-10-27.

— ReadyStack · readystack.dev