Sign inSign up
mise logo

sbx/mise

Verified Publisher

By Docker, Inc

•Updated 1 day ago

The polyglot dev-tool version manager (https://mise.jdx.dev) — installs the mise CLI and wires...

Sandbox Kit
0

7.8K

sbx/mise repository overview

Digest

sha256:ea0855d1f626…

Size

58.8 MB

Schema

v3

Pushed

1 day ago

Specificationspec.yaml

MIXIN

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.


Arguments
NameRequiredDefaultDescription
versionRequired—

mise release to install



CapabilitiesExpand a row to see its full configuration. See the full spec for the complete descriptor.
TypeRequiredDescription
com.docker.sandbox/network-policy@1Required—
com.docker.sandbox/lifecycle@1Required—

Requiresdeb/bash, deb/ca-certificates, deb/grep, deb/libc6, deb/libgcc-s1, deb/libssl3t64, deb/zlib1g, deb/libzstd1

Apply this mixin to a sandbox

sbx run <agent> --kit sbx/mise:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx⁠

⁠mise for Docker Sandboxes

This 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.

⁠Use

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⁠.

⁠Trust and downloads

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.

⁠References

See the Sandbox Kit v3 specification⁠, Docker Sandboxes documentation⁠, and Docker Hardened Images documentation⁠.