From 9fa8b5c1e37a13ec51e6fa84219191880238ca32 Mon Sep 17 00:00:00 2001 From: Joakim Persson Date: Mon, 20 Apr 2026 15:03:00 +0200 Subject: [PATCH] Fix misleading --rm wording: data loss happens on any container recreation --- DOCKER_HUB.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/DOCKER_HUB.md b/DOCKER_HUB.md index 2d79a36..8eb5167 100644 --- a/DOCKER_HUB.md +++ b/DOCKER_HUB.md @@ -237,10 +237,10 @@ Understanding what survives container restarts and what doesn't: - **Project files** (`/workspace`) are always safe — they're your host filesystem. - **opencode config** is auto-generated from `OPENCODE_PROVIDER` env var on each start if no existing config is found. To persist config changes, mount the config directory from the host (see Custom opencode Config below). -- **opencode data** (session history, memory) is lost with `--rm` unless you add a named volume. -- **TUI settings** (theme, toggles) are lost with `--rm` unless you add the `devbox-state` named volume. -- **Python installs** via `uv python install` are lost unless you add the `devbox-uv` named volume. -- **Rust toolchains** via `rustup-init` are lost unless you add the `devbox-rustup` and `devbox-cargo` named volumes. +- **opencode data** (session history, memory) is lost on container recreation unless you add a named volume. +- **TUI settings** (theme, toggles) are lost on container recreation unless you add the `devbox-state` named volume. +- **Python installs** via `uv python install` are lost on container recreation unless you add the `devbox-uv` named volume. +- **Rust toolchains** via `rustup-init` are lost on container recreation unless you add the `devbox-rustup` and `devbox-cargo` named volumes. - **AWS SSO tokens** persist across restarts when `~/.aws` is mounted (recommended for Bedrock users). ## Custom opencode Config