readystack/crowdsec repository overview

⁠CrowdSec (Local API)

readystack/crowdsec:v1.8.1-CE-ubuntu24.04-r2

A cosign-signed build of github.com/crowdsecurity/crowdsec v1.8.1 (MIT), built clean-room from official upstream source by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:4fa87a7561fbaccc7d77de92a5ffbe31ecb726587a7f4f113dab38a11ad969b3 on 2026-10-20.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with ce.rodeo's published rubric) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products.html#crowdsec⁠
• ReadyStack release check — passed at release on 2026-10-20: 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:4fa87a7561fbaccc7d77de92a5ffbe31ecb726587a7f4f113dab38a11ad969b3; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/crowdsec:v1.8.1-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (crowdsec).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.8.1-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 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.

• 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/crowdsec:v1.8.1-CE-ubuntu24.04-r2

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/crowdsec:v1.8.1-CE-ubuntu24.04-r2 (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 CrowdSec Local API (LAPI) only (crowdsec -c /etc/crowdsec/config.yaml -no-cs), with the cscli tool beside it. The LAPI stores decisions and alerts and answers the security bouncers that ask for ban decisions and the log-processing agents that send alerts. Its database is an embedded SQLite file, /var/lib/crowdsec/data/crowdsec.db, so there is no separate database, sidecar or web UI.

docker run -d --name crowdsec -p 8080:8080 -v crowdsec-data:/var/lib/crowdsec readystack/crowdsec:v1.8.1-CE-ubuntu24.04-r2

The metrics port 6060 is not published here: it answers without credentials, so let Prometheus reach it over a private Docker network, or publish it only on a trusted interface, e.g. -p 127.0.0.1:6060:6060.

⁠The full ReadyStack Agent-ready Archive

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 at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:430ac2cc02ba331f2c2139165c6c1eb898246c392d39e1ceee06085c69b74d30 on 2026-10-20.

— ReadyStack · readystack.dev