Container Fundamentals

Last updated Sep 28, 2026 A Cloudflare Container runs your container image in a full Linux environment on Cloudflare's network, alongside a Worker. The Worker handles incoming HTTP requests, while the Container provides the runtime, binaries, and languages your application needs. Together, they let you run Linux workloads without managing the underlying infrastructure.

The Container runtime

Run Linux workloads alongside your Worker.

A Worker runs code in an isolated JavaScript environment. A Container runs your image in a full Linux environment, so you can bring custom runtimes and binaries when your application needs them. Each Container instance runs inside its own virtual machine, which isolates it from other workloads. The Worker receives inbound HTTP requests and routes them to the Container, so the Container is not exposed directly to end users.

Play Reset

Request

WORKER

For more information, refer to Lifecycle of a Container.

How requests reach a Container

Route every request through your Worker.

The request begins at your Worker, which uses the Durable Object layer to identify and reach a Container. This layer coordinates routing and lifecycle behavior, allowing the Container to continue serving requests while it runs. A Container can start when it receives its first request, so the first request may take longer to complete.

Choose an instance identity to send a request

AB Reset

Request

WORKERRequest

WORKER

DURABLE OBJECTAROUTEHOOKSSLEEP

DURABLE OBJECTBROUTEHOOKSSLEEP

DURABLE OBJECTROUTEHOOKSSLEEP

DURABLE OBJECTROUTEHOOKSSLEEP

For more information, refer to Lifecycle of a Container.

Container lifecycle

Start on demand, then stop when idle.

A Container starts when your application needs it, so the first request can take longer while its environment starts. Once running, it serves requests until it becomes inactive; after an inactivity period, it can stop and release its running resources. When another request arrives, the Container can start again.

Play Reset

Request

Awaiting requestnothing runs untila request arrives

For more information, refer to Lifecycle of a Container and Pricing.

Sizing

Choose resources for your workload.

Container instance sizes let you match resources to your workload. You can choose a predefined size or configure a custom one, with larger sizes providing more CPU, memory, and disk. When choosing a size, consider the resources your application needs and refer to Limits and instance types for the available options and constraints.

For more information, refer to Pricing.

Placement

Place instances near users or within constraints.

Cloudflare places Container instances across its network, helping applications serve users from suitable locations. You can constrain placement by region or jurisdiction when your workload has location or data residency requirements. You can also run multiple instances when your application needs more capacity.

Choose a location
to send a request

Reset

Location A

Location B

Location C

Container

Container

Container

SchedulerSend requestSend requestSend request

For more information, refer to Placement.

Storage and connectivity

Keep durable data outside the local disk.

Treat a Container's local disk as temporary working space, because data on it can be lost when the Container stops or restarts. For data that must persist, use Durable Object storage or Cloudflare storage bindings such as KV, R2, and D1. Configured outbound handlers let the Container access these bindings and external services without requiring an SDK inside the Container.

Reset Play

Client

Worker

Container instancerunningimagemy-app:latestlocal disk

Persistent storage

KV

R2

D1

Durable Objects

Idle — click Next to step through the request

For more information, refer to Connect to Workers and bindings and Outbound traffic.

Start building

When you are ready to build, start with a deployed Container or explore the available guides.

Get started

Deploy your first container.

Guides

Task-focused walkthroughs for common container workloads.

Was this helpful?

YesNo

On this page

Container Fundamentals - 图1Docs

{"@context":"https://schema.org","@type":"WebPage","@id":"https://developers.cloudflare.com/containers/concepts/#page","headline":"Container Fundamentals","description":"Understand what a Cloudflare Container is, how requests reach it, how it starts and stops, where it runs, and how it holds state.","url":"https://developers.cloudflare.com/containers/concepts/","inLanguage":"en","image":"https://developers.cloudflare.com/containers/concepts/og.png?v=23cdeac259988f35","dateModified":"2026-09-28","publisher":{"@type":"Organization","name":"Cloudflare","description":"One platform for your apps, agents, and workforce. Build, secure, and scale without managing infrastructure","url":"https://www.cloudflare.com/","sameAs":["https://github.com/cloudflare","https://www.linkedin.com/company/cloudflare","https://x.com/cloudflare"],"logo":{"@type":"ImageObject","url":"https://developers.cloudflare.com/logo.svg"},"address":{"@type":"PostalAddress","streetAddress":"101 Townsend St","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94107","addressCountry":"US"},"contactPoint":[{"@type":"ContactPoint","contactType":"Customer Support","url":"https://support.cloudflare.com/","availableLanguage":["English"]},{"@type":"ContactPoint","contactType":"Sales","url":"https://www.cloudflare.com/contact/","availableLanguage":["English"]}]},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}

description: Understand how a Container is deployed, started, routed, and shut down across Cloudflare's network. title: Lifecycle of a Container image: https://developers.cloudflare.com/containers/concepts/architecture/og.png?v=9fb00333f140e961

Skip to content

Documentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/containers/llms.txt
Use this file to discover all available pages before exploring further.