E2B

​

Installation

pip install 'mirage-ai[e2b,ssh]'

pnpm add e2b ssh2

​

Usage

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

ws = Workspace(
    {"/data": RAMVFS()},
    mode=MountMode.EXEC,
    machines={
        "box": {
            "provider": "e2b",
            "sandbox_id": "sandbox-id",
            "mount_type": "ssh",
        }
    },
    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: 'e2b', sandboxId: 'sandbox-id', mountType: 'ssh' } },
    runtimes: [new MachineRuntime({ captures: ['@python', '@external'], machine: 'box' })],
  },
)
await ws.shell("python3 -c 'print(1 + 1)'")

mode: exec
machines:
  box:
    provider: e2b
    sandbox_id: ${E2B_SANDBOX_ID}
    mount_type: ssh
runtimes:
  - name: machine
    captures: ["@python", "@external"]
    machine: box
mounts:
  /data:
    vfs: ram

​

Connecting the workspace

​

ssh

• The template needs only sshfs (below). No Mirage, keys or open port in the sandbox.
• ssh and both do not work in browsers.
• Each file call is a round trip to the workspace, about 150 ms for a small file from a laptop; with both, keep bulk data on the sandbox’s own mounts.
• The sandbox shows one session’s view, the first that runs a line there. Give each agent its own sandbox.
• An sshfs still serving a path Mirage serves, another workspace’s or one of your own, is left alone and the line exits 1. Give each workspace its own sandbox.
• If the sandbox restarts, Mirage mounts the paths again. A line caught mid-restart exits 126 without running.
• The root mount and /dev are not served.

​

A template for ssh

from e2b import AsyncSandbox, Template

Template.build(Template().from_base_image().apt_install("sshfs"), "mirage-sshfs")
sandbox = await AsyncSandbox.create("mirage-sshfs")
print(sandbox.sandbox_id)

import { Sandbox, Template } from 'e2b'

await Template.build(Template().fromBaseImage().aptInstall('sshfs'), 'mirage-sshfs')
const sandbox = await Sandbox.create('mirage-sshfs')
console.log(sandbox.sandboxId)

​

fuse

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

mirage workspace create /tmp/sandbox.yaml

• This workspace’s rules do not reach those files, so a line is refused while the session’s permissions hide or narrow anything under them.
• If a path the sandbox mounted goes away, as on a restart, lines exit 126 until it is mounted again. Start Mirage from the image’s entrypoint so a restart mounts it again.
• Keep the sandbox’s paths in step with the host’s mounts yourself. sandbox.yaml can differ where it should, such as narrower credentials.

​

Runtime behavior

​

Notes

• Closing the workspace leaves the sandbox running.
• Output comes back as the program wrote it, binary included: the sandbox base64-encodes it on the way out, so the image needs dd and base64 (Debian, Ubuntu and Alpine images have both), and output takes about a third more to transfer. Without them a line runs nothing, prints why and exits 127.
• Commands run concurrently, each with its own input and output. Without piped input, stdin starts closed.
• Templates, sizing, networking and lifecycle stay E2B settings.
• A Mirage timeout tries to kill the command; its child processes may survive.