Skip to content
Cloud infrastructure/devops

bluemix.net:containers

IBM Containers sandbox and mock API

Containers are virtual software objects that include all the elements that an app needs to run. A container has the benefits of resource isolation and allocation but is more portable and efficient than, for example, a virtual machine. This documentation describes the IBM Containers API, which is based on the Docker Remote API. The API provides endpoints that you can use to create and manage your s Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
47
Collections
-
Event types
-
Start this simulation
example request
curl https://your-bluemix-containers.slurry.io/v3/containers/floating-ips \
  -H "Authorization: Bearer slurry_sim_..."

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

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 47.

  • POST/build
  • POST/containers/create
  • GET/containers/floating-ips
  • POST/containers/floating-ips/request
  • POST/containers/floating-ips/{ip}/release
  • GET/containers/groups
  • POST/containers/groups
  • GET/containers/groups/{name_or_id}
  • PATCH/containers/groups/{name_or_id}
  • DELETE/containers/groups/{name_or_id}
  • POST/containers/groups/{name_or_id}/maproute
  • POST/containers/groups/{name_or_id}/unmaproute