Containers
Define container images, resources, runtime limits, environment settings, and container-backed MCP servers.
Containers define isolated runtimes used by Workspace Agent sandboxes and container-backed Model Context Protocol (MCP) servers. Open Advanced → Containers to review each definition's status and creation or modification time.
Usually managed automatically
You normally do not need to create or maintain the default containers directly. Workspace setup creates the container that hosts the Workspace Agent sandbox. Adding a container-backed MCP Connection creates or selects the MCP server container it needs. Use this page for advanced runtime configuration, usage review, instance troubleshooting, or a custom container.
Page actions
| Action | What it does |
|---|---|
| New Container | Creates a custom or MCP-server container definition when automatic setup does not cover the runtime. |
| Browse MCP Server | Opens the catalog of container-backed MCP server templates. |
| View Instances | Shows runtime instances created when a Flow or Workspace uses a container. |
| Usage | Opens CPU, memory, storage, and runtime usage analytics. |
| Archive | Removes the selected container definition from active use. Check dependent Workspaces, Flows, and Connections first. |
Container definition
| Setting group | What it controls |
|---|---|
| Name, Description, Type | Identifies the container and chooses a Workspace, custom runtime, or MCP-server configuration. |
| Source | Builds from a Dockerfile or runs a Docker image. Public Docker Hub images and full ECR image URIs are supported by the form. |
| Environment template and values | Defines runtime inputs, required values, defaults, and secret fields. Keep credentials in secret fields. |
| CPU and Memory | Sets the resources available to each instance. The form shows compatible memory choices for the selected CPU size. |
| Max Lifetime | Stops an instance after its maximum total lifetime. 0 means no lifetime limit. |
| Idle Timeout | Stops an inactive instance after the configured duration. |
| Storage | Sets additional runtime storage when configured. |
| MCP Transport | For MCP servers, selects standard I/O, HTTP, or Server-Sent Events. HTTP and SSE also use a port and endpoint path. |
| Start Command | Supplies server startup arguments or commands when the image requires them. |
The editor shows an estimated hourly infrastructure cost. Actual use depends on the number of instances and how long they run. Use View Instances to find running or stopped instances and Usage to review consumption.