Skip to content

The image ghcr.io/chromadotnet/chromadotnet of the command - #169

Merged
Laurianti merged 1 commit into
mainfrom
native-image
Nov 15, 2026
Merged

Laurianti merged 1 commit into
mainfrom
native-image

Conversation

@Laurianti

Copy link
Copy Markdown
Member

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, with chromadotnet as the entrypoint and /data as 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, from alpine:3.24 pinned 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 --user for 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.

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.
@Laurianti
Laurianti requested a review from a team as a code owner November 15, 2026 16:07
@Laurianti
Laurianti merged commit f9a28e5 into main Nov 15, 2026
23 checks passed
@Laurianti
Laurianti deleted the native-image branch November 15, 2026 17:24
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