docs(docker): prefer writable named data volume
## Summary - Prefer a writable named Docker volume for the container home data path. - Document the non-root UID/GID ownership requirement for host bind mounts. - Update README and Docker docs examples to avoid permission-denied first runs. ## Test plan - git diff --check - GitHub CI green: version drift, lint, ubuntu, macOS, Windows, npm wrapper smoke, GitGuardian
This commit is contained in:
+1
-1
@@ -2,7 +2,7 @@
|
||||
# DeepSeek-TUI multi-arch Docker image (#501)
|
||||
#
|
||||
# Build: docker buildx build --platform linux/amd64,linux/arm64 -t deepseek-tui:latest .
|
||||
# Run: docker run --rm -it -e DEEPSEEK_API_KEY -v ~/.deepseek:/home/deepseek/.deepseek deepseek-tui
|
||||
# Run: docker run --rm -it -e DEEPSEEK_API_KEY -v deepseek-tui-home:/home/deepseek/.deepseek deepseek-tui
|
||||
#
|
||||
# The image ships both binaries (deepseek dispatcher + deepseek-tui runtime)
|
||||
# in a minimal runtime layer. No MCP servers or heavy toolchains are included
|
||||
|
||||
Reference in New Issue
Block a user