这份文档真正覆盖什么
Docker 文档说明了怎样在更可控的环境里运行 DeepSeek TUI,尤其适合依赖隔离或宿主机不稳定的场景。
怎么用这页
- 先看右侧目录,直接跳到你当前最关心的小节。
- 如果你只是来解决具体问题,优先读正文里的相关标题,再回站内对应 hub。
- 如果你要核对原始来源,可以直接打开 GitHub 原文链接。
Docker 文档说明了怎样在更可控的环境里运行 DeepSeek TUI,尤其适合依赖隔离或宿主机不稳定的场景。
Docker 文档说明了怎样在更可控的环境里运行 DeepSeek TUI,尤其适合依赖隔离或宿主机不稳定的场景。
DeepSeek TUI ships an official multi-arch Docker image (amd64 + arm64) on GitHub Container Registry.
docker run --rm -it \
-e DEEPSEEK_API_KEY="$DEEPSEEK_API_KEY" \
-v ~/.deepseek:/home/deepseek/.deepseek \
ghcr.io/hmbown/deepseek-tui:latest
Images are published to GitHub Container Registry (GHCR) only. Docker Hub publishing is not currently configured — add a docker/login-action step with Hub credentials to the release workflow if needed.
| Variable | Required | Description |
|---|---|---|
DEEPSEEK_API_KEY | yes | DeepSeek API key |
DEEPSEEK_BASE_URL | no | Custom API base URL (e.g. https://api.deepseek.com) |
DEEPSEEK_NO_COLOR | no | Set to 1 to disable terminal colour output |
Mount ~/.deepseek to persist sessions, config, skills, memory, and the offline queue across container restarts:
-v ~/.deepseek:/home/deepseek/.deepseek
Without this mount the container starts fresh each time.
When stdin is not a TTY, deepseek drops to the dispatcher's one-shot mode (deepseek -c "…"). Pipe a prompt on stdin:
echo "Explain the Cargo.toml in structured English." | \
docker run --rm -i -e DEEPSEEK_API_KEY ghcr.io/hmbown/deepseek-tui:latest
# Single platform (your host architecture)
docker build -t deepseek-tui .
# Multi-platform (requires a builder with emulation)
docker buildx create --use
docker buildx build --platform linux/amd64,linux/arm64 -t deepseek-tui .
The repository includes a .devcontainer/devcontainer.json configuration for VS Code / GitHub Codespaces. It pre-installs the Rust toolchain, rust-analyzer, and the deepseek binary. Open the repo in a devcontainer to get a ready-to-use development environment.
| Tag | Meaning |
|---|---|
latest | Latest stable release |
v0 | Latest v0.x release |
0.8.9 | Specific release version |
Docker images are built and pushed automatically when a release tag is pushed (see release.yml).