Apple Container

​

Installation

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

​

Usage

from mirage import RAMVFS, MountMode, Workspace
from mirage.runtime.machine import MachineRuntime

ws = Workspace(
    {"/data": RAMVFS()},
    mode=MountMode.EXEC,
    machines={"box": {"provider": "apple_container", "container": "my-sandbox"}},
    runtimes=[MachineRuntime(["@python", "@external"], machine="box")],
)
await ws.shell("python3 -c 'print(1 + 1)'")

import { MountMode, MachineRuntime, RAMVFS, Workspace } from '@struktoai/mirage-node'

const ws = new Workspace(
  { '/data': new RAMVFS() },
  {
    mode: MountMode.EXEC,
    machines: { box: { provider: 'apple_container', container: 'my-sandbox' } },
    runtimes: [new MachineRuntime({ captures: ['@python', '@external'], machine: 'box' })],
  },
)
await ws.shell("python3 -c 'print(1 + 1)'")

mode: exec
machines:
  box:
    provider: apple_container
    container: my-sandbox
runtimes:
  - name: machine
    captures: ["@python", "@external"]
    machine: box
mounts:
  /data:
    vfs: ram

​

Connecting the workspace

mounts:
  /data:
    vfs: s3
    config:
      bucket: my-bucket
    backend: fuse
    mountpoint: /data

container cp sandbox.yaml my-sandbox:/tmp/sandbox.yaml
container exec my-sandbox mirage workspace create /tmp/sandbox.yaml

• This workspace’s mount modes and permissions do not reach those files; sandbox.yaml decides.
• Keep the container’s paths in step with the host’s mounts yourself.

​

Runtime behavior

​

Notes

• Set container to the name of a running container.
• The image needs a POSIX-compatible /bin/sh. The session’s environment wins over the image’s. The working directory must already exist in the container.
• Host directories reach the container only through --volume. A service on your Mac is not at 127.0.0.1 inside; Apple’s host integration guide sets up host.container.internal.
• Each container is its own VM, so agents with one each share no files, processes, CPU or memory. Give each one that agent’s rules: the default profile in its sandbox.yaml.
• A timeout does not kill the program: container 1.4.1 does not deliver signals into the guest (apple/container#1941).