docs: match the Docker Swarm stack's ChromaDB server to the client the image ships and fix its Ollama and secret key settings - #1418
Open
silentoplayz wants to merge 1 commit into
Conversation
…e image ships and fix its Ollama and secret key settings
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.
Summary
I compared the Docker Swarm stack on both Swarm pages (the quick-start tab and the deployment guide) with what the Open WebUI image needs and with the Chroma 1.5.9 image.
chromadb==1.5.9client, which only speaks the v2 API. The image is now pinned to v1.5.9 and its data path moved to/data, which is where the v1 image'schroma run /config.yamlpersists. TheIS_PERSISTENT,ALLOW_RESETandPERSIST_DIRECTORYvariables of the old image are dropped. Thecurlhealthcheck is removed because the v1 runner image installs nocurl.OLLAMA_BASE_URLSbecameOLLAMA_BASE_URL. With only the plural set, the image's default/ollamais rewritten tohttp://host.docker.internal:11434. That rewritten value is whatRAG_OLLAMA_BASE_URLinherits. The Ollama embedding engine therefore pointed at a host that does not exist inside the stack.WEBUI_SECRET_KEY, so every task recreation signed everyone out. The deployment page already had it.WEBUI_NAMEis displayed with an " (Open WebUI)" suffix, now noted on the example value.Related issue or discussion
None.
Checklist
Notes for reviewers
Sources on
dev:backend/requirements.txtfor the chromadb pin,retrieval/vector/dbs/chroma.py,config.pyfor the Ollama URL rewrite andRAG_OLLAMA_BASE_URL,env.pyforWEBUI_NAME, andbackend/start.shfor the secret key file. For the Chroma side, I read the v1.5.9 image config from the Docker Hub registry (entrypointdumb-init -- chroma, commandrun /config.yaml), andrust/Dockerfileplusdocker_single_node.yamlat the v1.5.9 tag of chroma-core/chroma. I have not deployed the stack.