pi
1d1283f942
Re-point the re-brand at the new pi-only variant instead of with-pi, so pi-devbox stays a lean pi-focused image (no opencode) while the pi install logic still lives in one place upstream. This keeps pi-devbox meaningfully distinct from opencode-devbox:latest-with-pi. - Dockerfile: BASE_IMAGE default -> joakimp/opencode-devbox:latest-pi-only. - smoke-test.sh: size threshold 2900 -> 2750 MB (pi-only = with-pi minus opencode's ~145 MB binary). - Docs (README/AGENTS/DOCKER_HUB/CHANGELOG/docker-compose): drop the 'also contains opencode' notes; describe pi-only basis and the distinction from with-pi. Publish ordering unchanged: release opencode-devbox first so latest-pi-only carries the target pi version, then tag here (smoke asserts pi --version).
109 lines
6.2 KiB
Markdown
109 lines
6.2 KiB
Markdown
# pi-devbox
|
|
|
|
A Docker container with [pi coding-agent](https://github.com/earendil-works/pi) pre-installed, built on top of [opencode-devbox](https://hub.docker.com/r/joakimp/opencode-devbox)'s base image. Pi gets a fully-loaded development environment in one `docker run`.
|
|
|
|
## Image variants
|
|
|
|
| Tag | Size (compressed) | What you get |
|
|
|---|---|---|
|
|
| `joakimp/pi-devbox:latest` | ~700 MB | Pi + companion repos, on top of the opencode-devbox base |
|
|
| `joakimp/pi-devbox:vX.Y.Z` | same | Pinned pi version (tracks the [pi npm package version](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)) |
|
|
|
|
Multi-arch: `linux/amd64`, `linux/arm64`.
|
|
|
|
## Quick start
|
|
|
|
One-shot, no persistence:
|
|
|
|
```bash
|
|
docker run -it --rm \
|
|
-v "$PWD":/workspace \
|
|
-v "$HOME/.ssh":/home/developer/.ssh:ro \
|
|
-e ANTHROPIC_API_KEY="$ANTHROPIC_API_KEY" \
|
|
joakimp/pi-devbox:latest pi
|
|
```
|
|
|
|
For a fully-configured environment with persistent settings, MemPalace memory, neovim plugins, and shell history surviving container recreation, use docker-compose. **You don't need to clone the repo** — just grab two template files:
|
|
|
|
```bash
|
|
mkdir -p ~/pi-devbox && cd ~/pi-devbox
|
|
curl -O https://gitea.jordbo.se/joakimp/pi-devbox/raw/branch/main/docker-compose.yml
|
|
curl -fsSL https://gitea.jordbo.se/joakimp/pi-devbox/raw/branch/main/.env.example -o .env
|
|
# Edit .env — set WORKSPACE_PATH, an LLM API key (ANTHROPIC_API_KEY,
|
|
# OPENAI_API_KEY, GEMINI_API_KEY, or AWS_*), and your git identity.
|
|
docker compose run --rm devbox pi
|
|
```
|
|
|
|
Full setup guide — authentication for each provider (Anthropic, OpenAI, Gemini, AWS Bedrock SSO + static), persistence model, configuration reference, build args, troubleshooting: **<https://gitea.jordbo.se/joakimp/pi-devbox#readme>**
|
|
|
|
## What's inside
|
|
|
|
pi-devbox is a re-brand of the **opencode-devbox `pi-only` variant** — it builds
|
|
`FROM joakimp/opencode-devbox:latest-pi-only` and adds no layers of its own.
|
|
The pi-only variant is built `INSTALL_OPENCODE=false`, so this image is lean
|
|
and pi-focused (no opencode — use `opencode-devbox:latest-with-pi` if you want
|
|
both).
|
|
Everything below is inherited from that single source of truth.
|
|
|
|
Base tooling:
|
|
|
|
- **Debian trixie** (latest stable)
|
|
- **Node.js** (LTS), **uv** (Python tooling), **rustup** (Rust on-demand)
|
|
- **AWS CLI v2** + AWS Bedrock-ready config
|
|
- **MemPalace** + MCP server — persistent agent memory across sessions, queryable via `mempalace_*` tools inside pi
|
|
- **Gitea MCP** server
|
|
- **Dev tools**: neovim (LazyVim defaults), tmux, bat, eza, fzf, zoxide, ripgrep, git-lfs, make
|
|
- **Shell**: bash with history tuning, prefix-search bindings, fzf/zoxide integration
|
|
- **Host-OS-agnostic LAN access** — on VM-backed hosts (macOS OrbStack / Docker Desktop) the host is set up as an SSH jump to reach LAN peers (`dssh` alias; `DEVBOX_LAN_ACCESS`/`HOST_SSH_USER`). No-op on native Linux.
|
|
|
|
pi and companions:
|
|
|
|
- **pi** ([`@earendil-works/pi-coding-agent`](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)) — baked at `/usr/bin/pi`, version set by the pi-only base build
|
|
- **[pi-toolkit](https://gitea.jordbo.se/joakimp/pi-toolkit)** — keybindings (mosh/tmux-friendly Shift+Enter, Ctrl+J, Alt+J newline bindings), AWS env loader, settings template
|
|
- **[pi-extensions](https://gitea.jordbo.se/joakimp/pi-extensions)** — 7 user-facing extensions: `ext-toggle`, `mcp-loader`, `todo`, `ssh-controlmaster`, `notify`, `git-checkpoint`, `confirm-destructive`
|
|
- **`fork`** ([pi-fork](https://github.com/elpapi42/pi-fork)) and **`recall`** ([pi-observational-memory](https://github.com/elpapi42/pi-observational-memory)) tools
|
|
- **mempalace bridge** — MCP extension auto-symlinked so pi can read/write the same palace as opencode-devbox
|
|
|
|
The entrypoint deploys/registers all of these on first container start. Re-running is idempotent and preserves user edits.
|
|
|
|
## Versioning
|
|
|
|
Tags follow the pi npm version: `v0.74.0`, `v0.75.0`, etc. `latest` always points at the most recent release. The pi binary is inherited from `opencode-devbox:latest-pi-only`, so each release follows an opencode-devbox release that bakes the target pi version.
|
|
|
|
For container-level rebuilds on the same pi version (security updates, base bumps, fixes) the tag gets a letter suffix: `v0.74.0b`, `v0.74.0c`, …
|
|
|
|
## Persistent state
|
|
|
|
User edits and pi-installed packages survive container recreation when you mount these named volumes. Use the included `docker-compose.yml` and they're set up automatically.
|
|
|
|
| Volume | Mount point | What it holds |
|
|
|---|---|---|
|
|
| `devbox-pi-config` | `/home/developer/.pi/` | pi settings, extension toggles, sessions, user-installed pi packages (`npm install -g`, `pi install npm:…`) |
|
|
| `devbox-shell-history` | `/home/developer/.cache/bash` | bash history |
|
|
| `devbox-zoxide` | `/home/developer/.local/share/zoxide` | zoxide directory jump database |
|
|
| `devbox-nvim-data` | `/home/developer/.local/share/nvim` | neovim plugin & Mason package state |
|
|
| `devbox-uv` | `/home/developer/.local/share/uv` | uv Python installs and tool cache |
|
|
|
|
Optional volumes for MemPalace (commented out by default — uncomment in `docker-compose.yml` to persist conversation memory across restarts):
|
|
|
|
| Volume | Mount point | What it holds |
|
|
|---|---|---|
|
|
| `devbox-palace` | `/home/developer/.mempalace` | palace data (drawers, knowledge graph, embeddings) |
|
|
| `devbox-chroma-cache` | `/home/developer/.cache/chroma` | ChromaDB embedding model cache (~80 MB, can be rebuilt) |
|
|
|
|
## User-installed pi packages
|
|
|
|
`NPM_CONFIG_PREFIX` is set inside the container to `/home/developer/.pi/npm-global`. Anything you `pi install npm:<pkg>` or `npm install -g` lands on the `devbox-pi-config` named volume — survives container recreation **and** image rebuilds. A user-installed `pi` wins over the baked one via `PATH` order, so you can pin a different pi version without rebuilding the image.
|
|
|
|
## Source
|
|
|
|
- **This image**: https://gitea.jordbo.se/joakimp/pi-devbox
|
|
- **Base image**: https://gitea.jordbo.se/joakimp/opencode-devbox (Hub: `joakimp/opencode-devbox`)
|
|
- **pi**: https://github.com/earendil-works/pi
|
|
- **pi-toolkit**: https://gitea.jordbo.se/joakimp/pi-toolkit
|
|
- **pi-extensions**: https://gitea.jordbo.se/joakimp/pi-extensions
|
|
|
|
## License
|
|
|
|
MIT (the image; pi and the bundled tools each carry their own licenses).
|