readystack/cloudflared repository overview

⁠cloudflared

readystack/cloudflared:2026.10.5-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/cloudflare/cloudflared 2026.10.5 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Teams who want to publish or reach internal services through Cloudflare Tunnel without opening inbound firewall ports.

Why: cloudflared is the client for Cloudflare Tunnel. It makes outbound-only connections from your network, and requests for your services come back through them, so your servers need no public IP address.

Use case: A team runs an internal dashboard on a server with no public address. cloudflared on that network opens a Cloudflare Tunnel; users reach the dashboard through the tunnel, and the firewall keeps every inbound port closed.

About the upstream project, written from its own description: https://github.com/cloudflare/cloudflared⁠ · https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:992adb5925ee147a24a85632f2084db94b0b73520b2cc4472292b99b4a619a98 on 2026-10-28.

• 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/cloudflared⁠
• 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:992adb5925ee147a24a85632f2084db94b0b73520b2cc4472292b99b4a619a98; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/cloudflared:2026.10.5-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (cloudflared).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

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

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/cloudflared:2026.10.5-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 cloudflared (one static Go binary) as the non-root cloudflared user. It needs a Cloudflare account with a tunnel, and outbound Internet access to Cloudflare (port 7844, QUIC/UDP, falling back to HTTP/2 over TCP). There is no database, no web UI and no data directory; a tunnel run with a token keeps no state on disk.

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

# The tunnel token, the connector's credential; needed at every start.
TUNNEL_TOKEN=YOUR_TUNNEL_TOKEN

docker run -d --name cloudflared --restart unless-stopped --env-file ./cloudflared.env readystack/cloudflared:2026.10.5-CE-ubuntu24.04-r1

The image's default command is tunnel run; cloudflared reads the token from TUNNEL_TOKEN in cloudflared.env at every start. Get the token from the Cloudflare dashboard (Zero Trust > Networks > Tunnels) or with cloudflared tunnel token <name>. The tunnel's routes (public hostnames and the local services they reach) are configured in Cloudflare; a service on the Docker host is reached at host.docker.internal (add --add-host=host.docker.internal:host-gateway on Linux) or by putting cloudflared on the service's Docker network.

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

— ReadyStack · readystack.dev