docs: describe the rebuilt slim image, its size, and what to configure instead - #1388
Open
silentoplayz wants to merge 1 commit into
Open
docs: describe the rebuilt slim image, its size, and what to configure instead#1388silentoplayz wants to merge 1 commit into
silentoplayz wants to merge 1 commit into
Conversation
…o configure instead
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
The Docker tag page describes slim as the standard image minus the pre-downloaded model files, at about 1.5 GB, with identical packages, ffmpeg and pandoc. The
devbuilds after v0.11.3 rebuilt slim from the ground up. It now leaves out every local machine learning runtime and the packages that depend on one, and the compressed download is about 170 MB per architecture.This PR rewrites the slim sections of that page for the rebuilt image. The variant table row says what slim is for. An info admonition says this describes what
:dev-slimserves today and what:main-slimbecomes with the next release. It also says:main-slimis the previous slim until then, so the page stays true for someone pulling it this week. A table lists what is left out and what to configure instead, and the saving section now says slim always saves the download, since there are no models left to fetch.Related issue or discussion
None. The source is the rebuild itself. open-webui/open-webui@cb942bb added
requirements-slim.txtand the slim build path, and open-webui/open-webui@a1c0209 reworked the image layers, both on 2026-09-06.Checklist
Notes for reviewers
Sizes are compressed download sizes read from the registry manifests on 2026-09-10:
devdev-slimmain-slim(v0.11.3)Every row of the "what to use instead" table was checked against the slim-conditional code on
dev. That is the embedding, reranking and vector database branches inretrieval/utils.pyandretrieval/vector/factory.py, the loader fallback inretrieval/loaders/main.py, theVECTOR_DBdefault inconfig.py, the storage imports instorage/provider.py, and the package list inrequirements-slim.txt. The two 503 messages quoted in the table are the ones the code raises.