Cloudflare Worldedge community field guide

RETROSPECTIVE EDITION / 2026-03

Containers: keep the Worker as control plane

Full runtimes and filesystems belong behind explicit lifecycle, routing, resource, and shutdown controls.

ISSUE
27 / 32
FIRST PUBLISHED
SOURCE CHECKED
Archive integrity

The edition month is a curriculum position. This article was first published on 2026-08-10 and is not presented as a historical release or past activity.

01 / DECISION

When this primitive earns a place

Use Containers when code needs a Linux environment, specific runtime, filesystem, or resource profile that Workers alone should not emulate.

02 / ARCHITECTURE

Build the smallest defensible path

Let a Worker authenticate and route, derive stable container ownership, bound instance resources and concurrency, handle startup, and expose health plus shutdown.

  1. 01Name the contract

    Use Containers when code needs a Linux environment, specific runtime, filesystem, or resource profile that Workers alone should not emulate.

  2. 02Add one primitive

    Let a Worker authenticate and route, derive stable container ownership, bound instance resources and concurrency, handle startup, and expose health plus shutdown.

  3. 03Capture failure evidence

    Build reproducibly, scan dependencies, test cold start and health failure, cap resource use, and prove the Worker denies unauthorized routing.

03 / REPRODUCE

Evidence before confidence

Build reproducibly, scan dependencies, test cold start and health failure, cap resource use, and prove the Worker denies unauthorized routing.

npx wrangler containers list

04 / BOUNDARY

The production boundary

A container image expands the patch and supply-chain surface. Local disk and process state require explicit durability assumptions.

05 / FIRST-PARTY SOURCES

Keep first-party sources authoritative

Product behavior, limits, pricing, and availability can change. Re-check these sources before acting.

01 / SOURCECloudflare Containershttps://developers.cloudflare.com/containers/