:latest now resolves to the slim image (label 1.2.3-slim), so local-embeddings deployments crash-loop on startup
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, python
- Domain
- infrastructure, release
Research direction
Start with the Docker image publishing configuration and the release workflow that assigns the latest tag; the issue also points to hindsight-docs/docs/developer/installation.md under “Docker Image Variants.” Check how the 1.2.3 full and slim images are tagged and compare that with the documented variants. Done when latest resolves to the documented full image and the slim image has its own working tag.
Written by the indexing model from the issue text.
Description
Bug Description
The 1.2.3 release published the slim build to the :latest tag. docker pull ghcr.io/vectorize-io/hindsight:latest now yields an image labelled org.opencontainers.image.version=1.2.3-slim (0.56 GB amd64) whose venv has no torch, transformers or sentence-transformers. Any service that tracks :latest and uses local embeddings or the local reranker comes back with this on the next recreate:
File "/app/api/hindsight_api/engine/embeddings.py", line 390, in initialize
from sentence_transformers import SentenceTransformer
ModuleNotFoundError: No module named 'sentence_transformers'
ImportError: sentence-transformers is required for LocalSTEmbeddings. Install it with: pip install sentence-transformers
ERROR: Application startup failed. Exiting.
The container exits during lifespan, never binds :8888, and restart-loops. Nothing in the logs says the tag changed variant, so it reads as a broken local config — HINDSIGHT_API_EMBEDDINGS_PROVIDER=local is correct and was working minutes earlier.
The installation docs describe latest as the full image (~9 GB) and list slim as the separate variant
(hindsight-docs/docs/developer/installation.md, "Docker Image Variants"). The slim tag itself returns 404 on GHCR.
Steps to Reproduce
docker pull ghcr.io/vectorize-io/hindsight:latestdocker image inspect ghcr.io/vectorize-io/hindsight:latest --format '{{index .Config.Labels "org.opencontainers.image.version"}}'
→1.2.3-slim- Run it with local embeddings, e.g.
-e HINDSIGHT_API_EMBEDDINGS_PROVIDER=local -e HINDSIGHT_API_EMBEDDINGS_LOCAL_MODEL=<a sentence-transformers model dir>
(the defaultlocal/bge-smallpath fails the same way). - The API exits with the ImportError above.
Expected Behavior
latest is the full image, as documented, so an existing :latest deployment keeps working across an update. If the slim build is meant to become the default, the changelog says so and the startup failure names the variant instead of the missing module.
Actual Behavior
latest is the slim build. Deployments that track :latest with local embeddings break on their next pull or
compose re-create, including unattended updates driven from a UI. The only recovery available to the user is pinning a version tag, which the docs don't currently suggest.
Version
1.2.3
LLM Provider
Other
- Dominant language
- Python
- Stars
- 45.2k
- Forks
- 5.9k
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 355
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vectorize-io/hindsight
-
Hermes plugin: switch to stop mirroring built-in memory writes into the bank (mirror_builtin_memory)Openintegration:hermes
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vectorize-io/hindsight#6725 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6690 ·
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6683 ·
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6662 ·
Maintainers usually reply within 1 day
-
integration:hermes
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vectorize-io/hindsight#6658 · 1 comment ·
Maintainers usually reply within 1 day
All issues in vectorize-io/hindsight
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
abetlen/llama-cpp-python#2424 ·
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
jqueryscript/awesome-claude-code#1009 ·
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day