docs: clarify persistent container storage - #11190
Merged
Merged
Conversation
Document all stateful container paths, explain upgrade behavior and UnRAID mappings, and correct the obsolete troubleshooting mount target. Assisted-by: Codex:gpt-5
localai-org-maint-bot
force-pushed
the
bot/issue-6924-container-persistence
branch
from
July 29, 2026 14:03
4a9027e to
3c0bc0c
Compare
localai-bot
added
the
kind/documentation
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
3 participants
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.
Description
This PR fixes #6924 by documenting the four container paths that must be persisted across container recreation and image upgrades. It also:
/build/modelstroubleshooting mount target to/modelsNotes for Reviewers
Validation:
git diff --checkSigned commits