chroma-core/chroma

[Bug]: dev Docker image returning the wrong version

Open

#1341 opened on Nov 7, 2023

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Rust (27,958 stars) (2,247 forks)batch import
buggood first issue

Description

What happened?

When running the (automatically build?) devel image and call the /version API endpoint, the last stable release version is returned.

Start the container with:

$> docker run --rm -p 8000:8000 ghcr.io/chroma-core/chroma:0.4.16.dev15

Run:

$> curl http://localhost:8000/api/v1/version
"0.4.15"

I would expect "0.4.16.dev15"

Versions

0.4.16.dev15

Relevant log output

No response

Contributor guide

Tech stack
dockerrust
Domain
backenddevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of Dockerfamiliarity with REST APIs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate how the version is set in the Docker build for dev images. The issue is that the /api/v1/version endpoint returns the last stable release version (0.4.15) instead of the dev version (0.4.16.dev15). Look at the Dockerfile and any build scripts that set the version string (e.g., environment variables or build args). Also check the version endpoint implementation in the Rust backend to see how it retrieves the version. Ensure that for dev images, the version is set correctly during build.