Images¶

An image (a.k.a. stack) is the base filesystem a machine boots from. Choose one with the stack field when creating a machine.

List images¶

GET /v1/images

Scope: read or full.

curl https://api.sistemo.io/v1/images \
  -H "Authorization: Bearer $SISTEMO_API_KEY"

{
  "images": [
    { "name": "base", "display_name": "Base (Python + Node)", "is_default": true,  "status": "ready" },
    { "name": "python", "display_name": "Python", "is_default": false, "status": "ready" },
    { "name": "node", "display_name": "Node.js", "is_default": false, "status": "ready" },
    { "name": "debian13", "display_name": "Debian 13", "is_default": false, "status": "ready" },
    { "name": "ubuntu24.04", "display_name": "Ubuntu 24.04 LTS", "is_default": false, "status": "ready" }
  ]
}

The catalog¶

`stack`	Contents
`base` (default)	Debian + Python and Node preinstalled
`python`	Python toolchain
`node`	Node.js toolchain
`debian13`	Debian 13 (trixie), minimal
`ubuntu24.04`	Ubuntu 24.04 LTS

Use one¶

curl -X POST https://api.sistemo.io/v1/machines \
  -H "Authorization: Bearer $SISTEMO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stack":"python"}'

Sandbox(stack="python")          # Python SDK

Sandbox.create({ stack: "python" })   // JS SDK

If you omit stack, the default (base) is used. An unknown stack falls back to the server default.

Custom images (bring-your-own Docker image) are on the roadmap; today, pick from the catalog above. Self-hosted users can build their own images.