Apple Container

Start the container yourself. Apple’s container needs Apple silicon and macOS 26 or later; live FUSE mounts need SYS_ADMIN. Details: Python · TypeScript. Run these commands from the Mirage repository root:

brew install container
container system start
container build -f docker/sandbox/Dockerfile --target fuse \
  -t mirage-python-fuse .
container run -d --cap-add SYS_ADMIN \
  --name my-sandbox mirage-python-fuse sleep infinity

mirage-python-fuse is the local image name assigned by -t during the build. The image contains Python, Mirage, and FUSE (Filesystem in Userspace), which makes workspace backends accessible as ordinary files inside the container.

The example reuses Mirage’s shared Python image to serve workspace mounts inside the container. Your host application can use either SDK, including TypeScript; the two communicate through container exec.

Part of `container run`	Meaning
`-d`	Run the container in the background.
`--cap-add SYS_ADMIN`	Allow the FUSE mounts used to expose workspace files.
`--name my-sandbox`	Give this container a name; use it in the runtime’s `container` config.
`mirage-python-fuse`	Use the image built above.
`sleep infinity`	Keep the container running while Mirage sends commands through `container exec`.

This starts the container. Follow the Python or TypeScript guide above to copy your workspace configuration into it and mount your backends before running commands that use workspace files.

Python SDK
TypeScript SDK

from mirage.runtime.sandbox.apple_container import AppleContainerRuntime

runtime = AppleContainerRuntime(captures=["python3"], config={"container": "my-sandbox"})

import { AppleContainerRuntime } from '@struktoai/mirage-node'

const runtime = new AppleContainerRuntime({
  captures: ['python3'],
  config: { container: 'my-sandbox' },
})

Getting Started

Learn

Help

VFS

CLIs

Runtimes

Apple Container