jeena/opencode-container
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Run OpenCode inside an Arch Linux Docker container that closely mirrors a local development environment, while limiting access to sensitive files on the host.
9 commits 1 branch 0 tags 46 KiB
Find a file
Jeena a56da84b7a Prepopulate container-home with project dirs 
This is to fix the problem with docker creating those directories
to mount it inside of the container-home. This only happens when
the project path is inside of $HOME which is mounted to the
.local/share/opencode-container/cantainer-home

With it like this, the empty directories are owned by the local
user and not root and it's easier to clean up in the future.
2026-01-22 01:08:18 +09:00
.gitignore Fix container username and home mount 2026-01-21 23:58:15 +09:00
Dockerfile Replace docker compose with persistent per-project lifecycle 2026-01-21 21:33:30 +09:00
force-cleanup.sh Add cleanup script 2026-01-22 00:29:20 +09:00
opencode-container.py Prepopulate container-home with project dirs 2026-01-22 01:08:18 +09:00
opencode.aliases Replace docker compose with persistent per-project lifecycle 2026-01-21 21:33:30 +09:00
README.md Fix container username and home mount 2026-01-21 23:58:15 +09:00

README.md

opencode-container

Run OpenCode inside an Arch Linux Docker container that closely mirrors a local development environment, while limiting access to sensitive files on the host.

Features

  • Arch Linux–based image
  • Runs as the host user (same username, UID, GID)
  • Mounts only the current project directory (same absolute path inside container)
  • Persists OpenCode state in XDG_DATA_HOME/opencode-container/container-home directory
  • No access to SSH keys, passwords, or full $HOME
  • Simple shell function (opencode) to launch interactively

Install

Change to your projects directory and clone the repository:

cd ~/Projects/
git clone https://git.jeena.net/jeena/opencode-container.git

Source the helper file opencode.aliases in your shell configuration
(.bashrc or .zshrc) so the opencode function is available in new sessions.

We set up the XDG_DATA_HOME/opencode-container/container-home directory as a central $HOME inside of the container, independent of the session or project directory we start in. This persists the whole $HOME from inside the container so everything OpenCode writes into config files, etc. persists there.

Environment Variables

  • XDG_DATA_HOME: Override default data directory (default: ~/.local/share)

Usage

From any project directory:

opencode

The image is built automatically on first use if it does not already exist.
OpenCode starts inside the container with the current directory mounted and set as the working directory.