Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Open source CLI · Linux & macOS

Work in containers.

Rooz runs your dev workspaces in containers, on a local or remote Docker/Podman engine. Git cloning, SSH keys, encrypted secrets, shared caches, sidecars and declarative config are built in.

$curl -fsSL https://rooz.dev/install.sh | sh
Get started GitHub
Kangaroos carrying a shipping container
quick start
$ rooz system init                                   # SSH and age keys
$ rooz new -g [email protected]:your/repo myworkspace   # create a workspace from a repo
$ rooz enter myworkspace                             # open a shell in it
$ rooz code myworkspace                              # or open it in VS Code
$
Git built inClone a repo straight into the workspace volume - plus extra repos alongside it. SSH keysOne generated ed25519 key, mounted read-only into every work container. Git-safe secretsage-encrypted values in config. The identity never leaves your machine. Shared cachesPackage caches shared across workspaces, so builds stay warm. SidecarsDatabases and services next to your workspace - a minimal compose. Remote hostsShares as little as possible with the host, so workspaces run on remote engines too.

VS Code, inside the containerrooz code myworkspace attaches VS Code to the workspace. Extensions, terminals and debuggers run in the container; a volume keeps them across rebuilds.

Requirements

One of:

  • Docker >= 29.5.0
  • Podman >= 6

The engine must be yours: a rootless daemon on your machine, or a remote one only you use. Rooz protects your host, other workspaces and secrets from the repositories you open, but not from other users of the same engine - anyone with engine API access can read every volume, run containers on your networks and spoof image/volume names. Don’t share an engine with untrusted users.