container/create

When to Use

• CI/CD pipeline: Create a test container from the build image before running the test suite, allowing inspection of container config before starting.
• Ephemeral jobs: Create a single-use data processing container that runs one script and exits — then clean up with container/remove.
• Blue-green deployment: Create the new (blue) container with an updated image and port bindings before cutting over traffic from the current (green) container.
• Service provisioning: Create an isolated database container for a new tenant with dedicated volumes and environment-specific configuration.
• Scheduled jobs: Create a container for a nightly batch job, start it, collect output, then remove it — keeping the host environment clean.

Configuration

Connection Fields

Operation Fields

PortBindings Format

Map container ports to host ports. The key is {containerPort}/{protocol} and the value is an array of host binding objects:

{
  "8080/tcp": [{ "HostIp": "", "HostPort": "3000" }],
  "9229/tcp": [{ "HostIp": "127.0.0.1", "HostPort": "9229" }]
}

Volumes Format

Bind mounts and named volume mounts:

{
  "/app/data": {},
  "/app/config": {}
}

Sample Configuration

{
  "resource": "container",
  "operation": "create",
  "Image": "myapp:v2.2.0",
  "Name": "api-service-blue",
  "Env": [
    "NODE_ENV=production",
    "PORT=8080",
    "DB_URL={{ $credentials.dbUrl }}",
    "API_KEY={{ $credentials.apiKey }}"
  ],
  "PortBindings": "{\"8080/tcp\": [{\"HostIp\": \"\", \"HostPort\": \"3001\"}]}",
  "Volumes": "{\"/app/data\": {}, \"/app/logs\": {}}",
  "connection": {
    "dockerHost": "unix:///var/run/docker.sock",
    "connectionType": "unixsocket"
  }
}

Validation Errors

Output

Success Port

Error Port

On failure, the error port receives errorCode, message, resource, and operation. Handle CONFLICT separately if your workflow is idempotent — the container may already exist from a previous run.

Sample Output

{
  "containerId": "a1b2c3d4e5f67890abcdef1234567890abcdef1234567890abcdef1234567890",
  "containerName": "/api-service-blue",
  "warnings": [],
  "status": "success",
  "resource": "container",
  "operation": "create"
}

Expression Reference

Node Policies & GuardRails

Examples

Example 1: Blue-green deployment — create blue container

{
  "resource": "container",
  "operation": "create",
  "Image": "myapp:{{ $trigger.newVersion }}",
  "Name": "api-service-blue-{{ $trigger.deployId }}",
  "Env": [
    "NODE_ENV=production",
    "PORT=8080",
    "DB_URL={{ $credentials.dbUrl }}"
  ],
  "PortBindings": "{\"8080/tcp\": [{\"HostIp\": \"\", \"HostPort\": \"3001\"}]}"
}

Example 2: Ephemeral batch job container

{
  "resource": "container",
  "operation": "create",
  "Image": "batch-processor:stable",
  "Name": "batch-job-{{ $now | date('YYYYMMDD-HHmmss') }}",
  "Command": "[\"python\", \"run_batch.py\", \"--date\", \"{{ $trigger.batchDate }}\"]",
  "Env": [
    "S3_BUCKET={{ $vars.outputBucket }}",
    "AWS_ACCESS_KEY_ID={{ $credentials.awsKeyId }}",
    "AWS_SECRET_ACCESS_KEY={{ $credentials.awsSecretKey }}"
  ],
  "Volumes": "{\"/app/output\": {}}"
}

Example 3: Tenant database provisioning

{
  "resource": "container",
  "operation": "create",
  "Image": "postgres:15-alpine",
  "Name": "db-tenant-{{ $trigger.tenantId }}",
  "Env": [
    "POSTGRES_DB={{ $trigger.tenantId }}",
    "POSTGRES_USER=app",
    "POSTGRES_PASSWORD={{ $credentials.tenantDbPassword }}"
  ],
  "PortBindings": "{}",
  "Volumes": "{\"/var/lib/postgresql/data\": {}}"
}