Use this reference for containerized applications on the Workers platform, including container-enabled Durable Objects, lifecycle management, and request routing.

Choose the runtime

Use Containers for existing container images, custom runtimes, system dependencies, full filesystem access, or workloads needing additional CPU and memory. Use Workers when the application fits the Workers runtime without those requirements.

Containers are controlled through Durable Objects. An instance's identity does not make its filesystem persistent: design for restarts and store durable data outside the container disk. Read Container lifecycle and Container interface for the relationship between the process, its Durable Object, and persistent storage.

Find the documentation for the task

Read the linked page before writing code or configuration; use its current API, examples, and constraints rather than reconstructing them from memory.

Task	Start here
Create a project and deploy the first container	Get started
Configure images, bindings, instance sizes, and deployments	Configuration
Control startup, requests, lifecycle, and scheduling	API
Choose routing or connect other services	Patterns
Diagnose startup, persistence, capacity, or rollout issues	Gotchas

For additional topics, consult the Containers documentation index.