readystack/consul repository overview

⁠Consul

readystack/consul:v1.16.4-CE-ubuntu24.04-r5

Source, recipe and records

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

A cosign-signed build of github.com/hashicorp/consul v1.16.4 (MPL-2.0 — LAST open-source release before BUSL), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Operations and platform teams who run many services across servers, data centres or clusters that need to find each other.

Why: Consul keeps a registry of services. Services register themselves and find each other over DNS or HTTP, health checks keep traffic away from failing instances, and an HTTP API stores shared configuration.

Use case: A team runs internal services on virtual machines whose addresses change as machines are replaced. Each service registers with Consul and looks up the others by name over DNS; when an instance fails its health check, it drops out of the answers until it recovers.

About the upstream project, written from its own description: https://github.com/hashicorp/consul/blob/v1.16.4/README.md⁠ · https://developer.hashicorp.com/consul/docs/intro⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:02b29d477722cf4010a9a68a151fefaf321b3d6c239e839f8a87778a9086224f on 2026-11-03.

• 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/consul⁠
• ReadyStack release check — passed at release on 2026-11-03: 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:02b29d477722cf4010a9a68a151fefaf321b3d6c239e839f8a87778a9086224f; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/consul:v1.16.4-CE-ubuntu24.04-r5.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (consul).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.16.4-CE-ubuntu24.04-r5 — 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/consul:v1.16.4-CE-ubuntu24.04-r5

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/consul:v1.16.4-CE-ubuntu24.04-r5 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container, single static Go binary (CGO-free), foreground consul agent. Consul IS its own datastore (embedded raft + boltdb under -data-dir). Service discovery + health checking + KV store + DNS (:8600) + HTTP API (:8500). NO SQL DB, NO sidecar. The web UI is in the binary (the UI build upstream committed to the v1.16.4 tree) and is served at http://:8500/ui/ when the agent runs with -ui or -dev (this image's default command uses -dev).

docker run -d readystack/consul:v1.16.4-CE-ubuntu24.04-r5

⁠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/consul⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:86c509354da0cb8e5f2741148f06ee8c1a0d18589f0618cdc6f66f80d75614a6 on 2026-11-03.

— ReadyStack · readystack.dev