joakimp/mempalace-toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

contrib: clarify when opencode-devbox bakes in the toolkit

Browse Source 
Previous wording claimed opencode-devbox "bakes it in via
mempalace-toolkit" as if that were always true, but until
opencode-devbox v1.14.30b the image only shipped the mempalace
Python package, not the toolkit wrappers. Users following the
*-devbox scheduler docs on earlier images would hit
"mempalace-session: command not found" inside the container.

Rewrite the precondition to:
  - Name the version where bake-in starts (v1.14.30b).
  - Link to the upstream INSTALL_MEMPALACE_TOOLKIT build arg.
  - Document the escape hatch for custom/older containers
    (./install.sh --yes) and flag its ephemeral nature, so nobody
    leans on the manual install as a long-term solution.

Caught during 2026-04-30 runtime validation of the *-devbox
systemd unit on a freshly-rebuilt container.
This commit is contained in:
Joakim Persson
2026-04-30 20:57:13 +00:00
parent 46bcce5a67
commit 00ce8a7fa1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
contrib/README.md
+1 -1
View File
@@ -203,7 +203,7 @@ If you run opencode inside a long-lived container like [opencode-devbox](https:/
Preconditions:
- **Long-lived container.** `docker compose up -d` with `restart: unless-stopped` (or equivalent). If the container is ephemeral (per-invocation), this pattern doesn't apply.
- **`mempalace-session` is already installed inside the container.** opencode-devbox bakes it in via `mempalace-toolkit`, so a running devbox already satisfies this.
- **`mempalace-session` is already installed inside the container.** opencode-devbox bakes it in from `v1.14.30b` onward (see the [`INSTALL_MEMPALACE_TOOLKIT`](https://gitea.jordbo.se/joakimp/opencode-devbox#build-args) arg). For earlier images or custom containers without the toolkit installed, run `./install.sh --yes` from a `mempalace-toolkit` checkout inside the container first — the installer is idempotent and safe to re-run. Note that a manual install lives in the container's ephemeral layer and is lost on `docker compose up --force-recreate`, so the bake-in approach is the durable solution.
- **Host user can talk to docker.** Member of the `docker` group on Linux, or Docker Desktop running under the current login session on macOS.
- **Canonical container name is `opencode-devbox`.** If you renamed it via `container_name:` or docker-compose project naming, adjust `CONTAINER` in the template.