Correct Docker image path for latest release (v0.31.0)? ghcr.io/chopratejas/headroom:latest seems stuck at v0.27.0

[nick1714]

Hi, I've been running Headroom via Docker for about a month (following the README instructions) and wanted to update to the latest release, but I'm running into something confusing.

I'm currently on v0.27.0, and I tried the standard update path:

'docker pull ghcr.io/chopratejas/headroom:latest'

latest: Pulling from chopratejas/headroom
Digest: sha256:50b85d8e320cfcdf1b38919bb7ae067b93ff7a8de0a93f05b2c1246370200d1c
Status: Image is up to date for ghcr.io/chopratejas/headroom:latest

Docker says the image is already up to date, but the container is still v0.27.0 — the latest GitHub release is v0.31.0 (2026-07-09), so latest doesn't seem to be tracking releases anymore.

I also tried pinning a versioned tag directly, but neither exists on that registry path:

powershelldocker pull ghcr.io/chopratejas/headroom:v0.31.0 # not found
docker pull ghcr.io/chopratejas/headroom:0.31.0 # not found

I noticed the repo moved from chopratejas/headroom to the headroomlabs-ai org, and the Docker Actions workflow still looks active (lots of recent runs), so I'm guessing the image is now being published somewhere else and the docs just haven't caught up yet.

Questions:

Is there a new/correct image path I should be pulling from instead of ghcr.io/chopratejas/headroom?
If not, is latest expected to be updated again soon, or should we be building from source in the meantime (docker buildx bake runtime-default)?

Would appreciate a pointer if anyone (maintainers or other Docker users) knows the current setup — happy to update the README/docs myself via PR once I know the right path.

Thanks!

[yurefr]

I just tried updating to 0.32 and noticed the same problem; I never checked the version—I just ran docker pull thinking everything was fine—but today I looked and I'm still on 0.27. I need an answer too.

[chopratejas]

Let me look into this.

[chopratejas]

cc: @JerrettDavis @DevanshiVyas - can you help out here?

[MentalOfCrow]

The image path changed when the repository moved to the headroomlabs-ai organization. The current Docker workflow derives the image name from ${{ github.repository }}, so the current package is:

docker pull ghcr.io/headroomlabs-ai/headroom:0.32.0
# or, if you intentionally want the moving release tag:
docker pull ghcr.io/headroomlabs-ai/headroom:latest

The old ghcr.io/chopratejas/headroom:latest package is a different GHCR namespace, so pulling it can keep returning the last image published there (0.27.0).

This is also consistent with the project's current workflow: the v0.32.0 release Docker run completed successfully, versioned releases are tagged with the release version, and the final promote-latest job points latest at that version.

You can confirm what is running with:

docker image inspect ghcr.io/headroomlabs-ai/headroom:0.32.0 \
  --format '{{ index .Config.Labels "org.opencontainers.image.version" }}'

The Docker installation page still contains the old personal namespace, so that documentation appears to be stale rather than the 0.31.0/0.32.0 images being missing.

If this fixes the pull for you, please mark the comment as the accepted answer so future users who find the old path can locate the correction quickly.

[yurefr]

It worked! I'm now using version 0.32.0 with the variant I usually use, "/headroom:code". It should work fine now. Thanks!