readystack/coredns repository overview

⁠CoreDNS

readystack/coredns:v1.14.2-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/coredns/recipe⁠
• Upstream source at this release's pinned commit (v1.14.2): https://github.com/coredns/coredns/tree/dd1df4f5db93767a44e37638df44969503b320d2⁠
• Product page: https://readystack.dev/products/coredns⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/coredns⁠
• Release history (JSON): https://readystack.dev/api/releases/coredns⁠
• Defect record: https://readystack.dev/defects.html?product=coredns⁠
• Today's scan: https://readystack.dev/products/coredns#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=coredns⁠
• 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/coredns/coredns v1.14.2 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Platform engineers and network administrators who run DNS for Kubernetes clusters or internal networks.

Why: CoreDNS is a DNS server built from plugins. It can serve zone files, forward and cache queries, and answer for Kubernetes services, each feature switched on in its configuration file.

Use case: In a Kubernetes cluster, CoreDNS answers pods' lookups for the cluster's service names and forwards other names to upstream resolvers. On an office network, the same server can serve internal names from a zone file and cache lookups for everything else.

About the upstream project, written from its own description: https://github.com/coredns/coredns⁠ · https://coredns.io/manual/toc/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:2b014072549ccd0ee67a40fcb34c99b2694bf51d2a62356cb12a8e1ce6d44145 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/coredns⁠
• ReadyStack release check — passed at release on 2026-10-29: 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:2b014072549ccd0ee67a40fcb34c99b2694bf51d2a62356cb12a8e1ce6d44145; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/coredns:v1.14.2-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (65532:65532).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.14.2-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/coredns:v1.14.2-CE-ubuntu24.04-r1

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/coredns:v1.14.2-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 the CoreDNS DNS server as the non-root user 65532 (nonroot). /coredns carries the file capability cap_net_bind_service, so the non-root process can bind port 53 without root. The default command is -conf /etc/coredns/Corefile: the image's Corefile answers every query with CoreDNS's whoami plugin (upstream's own default) and serves /health on 8080 and /ready on 8181. Mount your own Corefile at /etc/coredns/Corefile, as Kubernetes does with its coredns ConfigMap. Arguments after the image name replace the default command, so repeat -conf /etc/coredns/Corefile before any extra flag.

docker run -d --name coredns -p 53:53/udp -p 53:53/tcp readystack/coredns:v1.14.2-CE-ubuntu24.04-r1

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

— ReadyStack · readystack.dev