readystack/caddy repository overview

⁠Caddy

readystack/caddy:v2.11.4-CE-ubuntu24.04-r2

A hardened, cosign-signed, offline-rebuildable build of github.com/caddyserver/caddy v2.11.4 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

• Docker Scout — re-checked daily; today's grade and the reason for it are at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key; verify with cosign verify --key https://readystack.dev/keys/cosign.pub --insecure-ignore-tlog=true readystack/caddy:v2.11.4-CE-ubuntu24.04-r2.
• Built from source, non-root.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v2.11.4-CE-ubuntu24.04-r2 — the release on sale at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is hermetically built, signed, attested, and supported under your 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 patched or re-graded: move to the current release. A superseded release's build kit is available through 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/caddy:v2.11.4-CE-ubuntu24.04-r2

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

Each release tag is signed; verify with cosign verify --key https://readystack.dev/keys/cosign.pub --insecure-ignore-tlog=true readystack/caddy:v2.11.4-CE-ubuntu24.04-r2 (ReadyStack keeps signatures off the public transparency log, so the check is key-only). Support: [email protected]⁠.

⁠Deployment

Single container, single static binary, foreground process. No sidecars, no DB.

docker run -d --name caddy -p 80:80 -p 443:443 -v caddy_data:/data -v caddy_config:/config readystack/caddy:v2.11.4-CE-ubuntu24.04-r2

Starts Caddy in the foreground as PID 1, serving the shipped default Caddyfile: GET / returns a placeholder page and GET /health returns 200 OK (tested, both within a second of start). Persist /data (certificates and ACME state) and /config (autosaved JSON config) with named volumes, as in run_command — tested to survive docker rm + a fresh docker run on the same volumes. The admin API on :2019 binds to localhost INSIDE the container only (see Admin api in the handbooks) — publishing it to the host does not make it reachable from outside the container. The archive ships no Compose file.

⁠The full ReadyStack Agent-ready Archive

The complete --network=none build kit to recreate this exact image yourself — plus admin/DB/API handbooks, seed data, a validated test suite, and signed provenance — is at readystack.dev/buy.html⁠.

— ReadyStack · readystack.dev