readystack/traefik repository overview

⁠Traefik

readystack/traefik:v3.7.16-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/traefik/traefik v3.7.16 (MIT), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Teams running services on container platforms such as Kubernetes who want routing that follows services as they change.

Why: Traefik is an HTTP reverse proxy and load balancer that reads your infrastructure, such as Kubernetes, and configures its routes automatically and dynamically, including HTTPS certificates.

Use case: A team deploys new microservices to Kubernetes every week. Each service declares its host name in its own configuration; Traefik notices it, starts routing traffic to it and obtains a certificate for it, with no edits to a central proxy configuration.

About the upstream project, written from its own description: https://github.com/traefik/traefik⁠

⁠What you get

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

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v3.7.16-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/traefik:v3.7.16-CE-ubuntu24.04-r1

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

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

Single container, single static binary, foreground process. No relational database, no user accounts. Only the FILE provider is enabled by default (--providers.file.filename=/etc/traefik/traefik-dynamic.yml, baked into the image's ENTRYPOINT; the shipped file is an empty configuration, {}); the docker, kubernetes and other providers are off until you add their flag as an extra command-line argument (see Docker provider in the handbooks). Mounting /var/run/docker.sock by itself changes nothing (tested).

docker run -d --name traefik -p 80:80 -p 443:443 -p 127.0.0.1:8080:8080 readystack/traefik:v3.7.16-CE-ubuntu24.04-r1

Starts Traefik in the foreground as PID 1. Port 80 is the web entrypoint, 443 is websecure, and 8080 carries the REST API and dashboard together — published to 127.0.0.1 only here because that API has no authentication at all (see Administrator password in the handbooks). GET http://127.0.0.1:8080/ping⁠ answered 200 OK about 1-2 seconds after start in testing. The baked dynamic-config file is an empty configuration ({}), so nothing is actually routed until you add configuration (see File provider or Docker provider in the handbooks). 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 a free download for any registered account at readystack.dev/products/traefik⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:f3d711110aab6de0a6062da2f35c31b3b3d18bc0b9eadbc95c03dff9ec7bbd81 on 2026-10-28.

— ReadyStack · readystack.dev