docker.com:engine

Docker Engine sandbox and mock API

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses s Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations: 104
Collections: -
Event types: -

Start this simulation

example request

curl https://your-docker-engine.slurry.io/v1.33/_ping \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.33.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

State. Creates, updates and deletes persist and show up in later reads.
Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
Webhooks. Every change emits a signed, retried event.
Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 104.

GET/_ping
POST/auth
POST/build
POST/build/prune
POST/commit
GET/configs
POST/configs/create
GET/configs/{id}
DELETE/configs/{id}
POST/configs/{id}/update
POST/containers/create
GET/containers/json