The polyglot dev-tool version manager (https://mise.jdx.dev) — installs the mise CLI and wires...
7.8K
The polyglot dev-tool version manager (https://mise.jdx.dev) — installs the mise CLI and wires up shell activation so the agent can run `mise install`, `mise use`, and per-project `.mise.toml` resolutions in the sandbox.
| Name | Required | Default | Description |
|---|---|---|---|
version | Required | — | mise release to install |
[email protected]| Type | Required | Description | |
|---|---|---|---|
com.docker.sandbox/network-policy@1 | Required | — | |
com.docker.sandbox/lifecycle@1 | Required | — | |
deb/bash, deb/ca-certificates, deb/grep, deb/libc6, deb/libgcc-s1, deb/libssl3t64, deb/zlib1g, deb/libzstd1sbx run <agent> --kit sbx/mise:latestRun the following command to install sbx on your machine.
brew install docker/tap/sbxwinget install Docker.sbxThis mixin Kit adds mise, the polyglot development tool manager, to a compatible workload. Keep
tool versions in your project’s mise.toml, .mise.toml, or .tool-versions file and run mise install inside the
sandbox. It does not choose or preinstall your project toolchain.
This Kit is built on Docker Hardened Images.
Add --kit sbx/mise when creating a sandbox with a workload such as Shell. The
mixin keeps the workload’s command, user, and home directory. The existing DHI mise catalog image remains a standalone
tool.
Run mise --version, then mise install in your project directory. Shell activation appends to the agent’s .bashrc
without replacing it. Login and non-interactive Bash shells also receive the mise shims through the workload’s
persistent shell environment. Zsh and Fish users should follow
mise’s activation instructions.
The Kit pre-trusts project configuration with MISE_TRUSTED_CONFIG_PATHS=/, because the attached workspace already runs
inside the sandbox. Mise configuration can execute commands. Narrow that setting yourself if your workspace needs a
smaller trust boundary.
The mise binary arrives in the Kit artifact and uses the workload's Debian 13 native libraries. Sandbox creation
requires no download. Runtime grants cover only github.com, api.github.com, objects.githubusercontent.com, and
release-assets.githubusercontent.com, for GitHub-hosted tool releases. Other backends need explicit runtime policy
grants for the hosts they use, such as nodejs.org for Node. Add only the destinations your project needs.
See the Sandbox Kit v3 specification, Docker Sandboxes documentation, and Docker Hardened Images documentation.