readystack/argocd repository overview

⁠Argo CD

readystack/argocd:v3.5.6-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of Argo CD v3.5.6, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Platform and DevOps teams who deploy applications to Kubernetes clusters.

Why: Argo CD treats a Git repository as the source of truth for what should run. It compares each cluster with Git, shows the differences, and syncs the cluster back to the declared state.

Use case: A team keeps the manifests for its services in Git. A change merged there is what reaches staging and production: Argo CD notices the new target state and applies it, and if someone edits a cluster by hand, the application shows as out of sync until it is brought back in line.

About the upstream project, written from its own description: https://github.com/argoproj/argo-cd⁠ · https://argo-cd.readthedocs.io/en/stable/⁠

⁠What you get

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

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

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

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/argocd:v3.5.6-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 self-contained container. The Argo CD components (argocd-server, argocd-repo-server, argocd-application-controller) and redis run INSIDE this one image under supervisord, next to an embedded k3s that serves as the Kubernetes API and datastore. There is no argocd-dex-server in this image (no dex process; /api/dex answers 404). This is NOT a Kubernetes deployment / Helm install / kubectl apply of the install manifests — the image IS the complete running instance. Argo CD can manage external clusters once you register them, but the control plane itself is this one container.

docker run -d --name argocd -p 8080:8080 readystack/argocd:v3.5.6-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/argocd⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:d00b764258e960d407491bf5652e5ae5c5f5349f55fec467c9ded981927f7df5 on 2026-10-29.

— ReadyStack · readystack.dev