readystack/qdrant repository overview

⁠Qdrant

readystack/qdrant:v1.20.0-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of https://github.com/qdrant/qdrant⁠, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Developers building semantic search, recommendations or retrieval for AI applications.

Why: Qdrant is a vector database and similarity search engine. It stores vectors with a payload, finds the closest matches to a query vector, and filters results on the payload.

Use case: A support team wants its help-centre search to find articles by meaning, not exact words. Each article is turned into an embedding and stored in Qdrant with its product and language; a user's question is embedded the same way, and Qdrant returns the closest articles for that product.

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

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:525efd5dc93148a82e7bc63afc66c78a5d24a6473414c89f1bf951c6d47fc8e9 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/qdrant⁠
• ReadyStack release check — passed at release on 2026-10-27: 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:525efd5dc93148a82e7bc63afc66c78a5d24a6473414c89f1bf951c6d47fc8e9; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/qdrant:v1.20.0-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (qdrant).
• Built from source by ReadyStack; the web UI in /qdrant/static is upstream's prebuilt release https://github.com/qdrant/qdrant-web-ui/releases/download/v0.2.18/dist-qdrant.zip⁠ (sha256 fdce24c04ec1…).

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

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

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/qdrant:v1.20.0-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. Embedded on-disk storage, no datastore sidecar.

docker run -d --name qdrant -p 6333:6333 -p 6334:6334 -v qdrant_storage:/qdrant/storage readystack/qdrant:v1.20.0-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/qdrant⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:11453dc65b02207448d3caad2c61880302e69b7fc2b72e87dc361d6076ab7bbc on 2026-10-27.

— ReadyStack · readystack.dev