Skip to content

Conversation

bashofmann
Copy link
Contributor

This allows users to securely verify that a Qdrant container image was created by us

Once merged and after the next release, a container image can be verified like this:

cosign verify qdrant/qdrant:v1.16.0 --certificate-oidc-issuer=https://token.actions.githubusercontent.com --certificate-identity-regexp='https://github.com/qdrant/.*'

All the details: https://docs.sigstore.dev/cosign/signing/signing_with_containers/

All Submissions:

  • Contributions should target the dev branch. Did you create your branch from dev?
  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

This allows users to securely verify that a Qdrant container image was created by us
@bashofmann bashofmann requested a review from timvisee August 22, 2025 14:04
coderabbitai[bot]

This comment was marked as resolved.

coderabbitai[bot]

This comment was marked as resolved.

Comment on lines +59 to +61

DIGEST=$(docker buildx imagetools inspect ${DOCKERHUB_TAG} --format '{{ json .Manifest.Digest }}' | cut -d '"' -f 2)
cosign sign --yes "${DOCKERHUB_TAG}@${DIGEST}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it correct that we sign after pushing the image? Then, where is the signature kept?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is correct. The docker tag includes the registry host, and cosign attaches the signature for us.

@qdrant qdrant deleted a comment from coderabbitai bot Aug 25, 2025
@bashofmann bashofmann merged commit 4e8e9da into qdrant:dev Aug 25, 2025
16 checks passed
timvisee pushed a commit that referenced this pull request Aug 26, 2025
* Sign container images with cosign

This allows users to securely verify that a Qdrant container image was created by us

* Add contents read permission
@timvisee timvisee mentioned this pull request Aug 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants