Repository navigation
The image ghcr.io/chromadotnet/chromadotnet of the command - #169
Merged
Merged
Conversation
release-assets.yml builds it from the native file for linux-musl-x64 on Alpine 3.24, pushes it only with the tag of the version, signs it by its digest with cosign and attests its build provenance. The CI of every pull request builds the same Dockerfile and runs it against Chroma 1.5.9.
ambergrove
approved these changes
Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Each release gets the image
ghcr.io/chromadotnet/chromadotnet, tagged only with its version: the native file for linux-musl-x64 on Alpine 3.24, withchromadotnetas the entrypoint and/dataas the working folder. It is only for linux/amd64, as there is no native file for musl on arm64.ChromaDB.Client.Cli/Dockerfile: the image, fromalpine:3.24pinned by its digest.release-assets.yml: after the files of the release are uploaded, it builds the image from the file of the same CI run, pushes it, signs it by its digest with cosign and attests its build provenance.ci.yml: the job for linux-musl-x64 builds the same Dockerfile and runs the backup, the restore and the verification against Chroma 1.5.9 with the image.docs/backup.md: how to run it, with--userfor the owner of the mounted folder.Tested: the image built from the native file of the CI of
main, run against Chroma 1.5.9 with a backup, a restore and a verification, also as a user that is not root; and it reaches Chroma Cloud over HTTPS: a wrong key gets the answer of Chroma Cloud.