Further progress

Author: mikenomitch

src/content/docs/containers/containers-api.mdx

@@ -11,6 +11,17 @@ sidebar:
 
 import { GlossaryTooltip, ListExamples } from "~/components";
 
-Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Containers.
+Container Examples are Coming Soon!
+
+{/* Examples to add:
+- Statelss routing (FFMPEG)
+- Stateful app
+- Regional placement
+- Workflow Integration
+- Queue Integration
+- AI-generated code execution
+- Batch Workload for CI (chaining multiple) */}
+
+{/* Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Containers. */}
 
 <ListExamples directory="containers/examples/" />

src/content/docs/containers/examples/index.mdx

@@ -10,7 +10,9 @@ In this example, each container runs a small webserver written in Go.
 
 Requests are initially handled by the Worker, then passed to container-enabled [Durable Objects](/durable-objects).
 Each Durable Object runs alongside a container, manages starting and stopping it, and
-can interact with the container through its ports.
+can interact with the container through its ports. Containers will likely run near the Worker instance
+requesting them, but not necessarily. See ["How Locations are Selected"](/containers/reference/platform-details/#how-are-locations-are-selected)
+for details.
 
 In a simple app, the Durable Object may just boot the container and proxy requests to it.
 

src/content/docs/containers/get-started.mdx

@@ -1,8 +1,8 @@
 ---
 pcx_content_type: reference
-title: Private Beta Info
+title: Closed Beta Info
 sidebar:
-  order: 6
+  order: 1
 ---
 
 Currently, Containers are in private beta. We plan to make Containers available in open beta in several months.
@@ -17,8 +17,8 @@ There are several known changes we plan to make prior to open beta, as well as m
 We plan to make the following changes:
 
 - Add Logs to the Dashboard
-- Add autoscaling and load balancing to Containers
-- Add atomic Worker updates so Worker code and Container code stay in sync
+- Add autoscaling and load balancing to Containers, using the interface `env.MY_CONTAINER.fetch()`
+- Ensure Worker code and Container code stay in sync with atomic code updates
 - Improve the local dev experience
 - Expose more information on Container Settings in the dashboard
 - Increase limits on number of containers and container size
@@ -46,3 +46,5 @@ There are several areas where we wish to gather feedback from users:
 - Do you need different mechanisms for routing requests to containers?
 - Do you need different mechanisms for scaling containers?
 - Do you want to integrate Containers with any other Cloudflare services? If so, which ones and how?
+
+At any point during the Beta, feel free to [give feedback using this form](https://forms.gle/CscdaEGuw5Hb6H2s7).

src/content/docs/containers/reference/closed-beta-info.mdx

@@ -2,19 +2,22 @@
 pcx_content_type: concept
 title: Limits
 sidebar:
-  order: 4
+  order: 3
 ---
 
 import { Render } from "~/components";
 
-Containers limits are detailed below.
+Containers limits are detailed below:
 
 | Feature                                | Workers Paid |
 | -------------------------------------- | ------------ |
 | Container Count                        | 10 [^1]      |
 | Max Concurrent Instances per Container | 20 [^1]      |
 | Max Concurrent Instances per Account   | 100          |
-| Images in Registry                     | X            |
-| Image Size                             | X            |
+| Images in Registry                     | None [^2]    |
+| Image Size                             | None [^2]    |
+| Unused Retention Period                | None [^2]    |
 
 [^1]: This limit will be raised as we continue the private beta.
+
+[^2]: There is currently no limit, but there will be in the future.

src/content/docs/containers/reference/limits.mdx

@@ -2,11 +2,41 @@
 pcx_content_type: navigation
 title: Platform Details
 sidebar:
-  order: 8
+  order: 2
   group:
     hideIndex: true
 ---
 
+This page contains various details about the Containers platform:
+
+## How locations are selected
+
+When initially deploying a Container, Cloudflare will select various locations across our
+network to deploy instances to. These locations will span multiple regions.
+
+When a Container instance is requested with `this.ctx.container.start`, the nearest free
+container instance will be selected from the pre-initialized locations. This will
+likely be in the same region as the external request, but may not be. Once the container
+instance is running, any future requests will be routed to the initial location.
+
+An Example:
+
+- A user deploys a Container. Cloudflare automatically readies instances across its Network.
+- A request is made from a client in Bariloche, Argentia. It reaches the Worker in
+  Cloudflare's location in Neuquen, Argentina.
+- This Worker request calls `MY_CONTAINER.get("session-1337")` which brings up a Durable
+  Object, which then calls `this.ctx.container.start`.
+- This requests the nearest free Container instance.
+- Cloudflare recognizes that an instance is free in Buenos Aires, Argentina, and
+  starts it there.
+- A different user needs to route to the same container. This user's request reaches
+  the Worker running in Cloudflare's location in San Diego.
+- The Worker again calls `MY_CONTAINER.get("session-1337")`.
+- If the initial container instance is still running, the request is routed to the location
+  in Buenos Aires. If the initial container has gone to sleep, Cloudflare will once
+  again try to find the nearest "free" instance of the Container, likely
+  one in North America, and start an instance there.
+
 ## Environment variables
 
 The container runtime automatically sets the following variables:

src/content/docs/containers/reference/platform-details.mdx

@@ -2,78 +2,18 @@
 pcx_content_type: reference
 title: Pricing
 sidebar:
-  order: 6
+  order: 4
 ---
 
-By default, all users are on the Images Free plan. The Free plan includes access to the transformations feature, which lets you optimize images stored outside of Images, like in R2.
+## Closed Beta Pricing
 
-The Paid plan allows transformations, as well as access to storage in Images.
+During the closed beta, Containers are free to run and images stored
+in the Cloudflare Registry are free of cost.
 
-Pricing is dependent on which features you use. The table below shows which metrics are used for each use case.
+Users will be charged standard pricing for both [Workers](/workers/platform/pricing/) and
+[Durable Objects](/durable-objects/platform/pricing/), both of which are necessary to
+interact with Containers.
 
-| Use case                                              | Metrics                         | Availability        |
-| ----------------------------------------------------- | ------------------------------- | ------------------- |
-| Optimize images stored outside of Images              | Images Transformed              | Free and Paid plans |
-| Optimized images that are stored in Cloudflare Images | Images Stored, Images Delivered | Only Paid plans     |
+## Long-term Pricing
 
-## Images Free
-
-On the Free plan, you can request up to 5,000 unique transformations each month for free.
-
-Once you exceed 5,000 unique transformations:
-
-- Existing transformations in cache will continue to be served as expected.
-- New transformations will return a `9422` error. If your source image is from the same domain where the transformation is served, then you can use the [`onerror` parameter](/images/transform-images/transform-via-url/#onerror) to redirect to the original image.
-- You will not be charged for exceeding the limits in the Free plan.
-
-To request more than 5,000 unique transformations each month, you can purchase an Images Paid plan.
-
-## Images Paid
-
-When you purchase an Images Paid plan, you can choose your own storage or add storage in Images.
-
-| Metric             | Pricing                                                                                    |
-| ------------------ | ------------------------------------------------------------------------------------------ |
-| Images Transformed | First 5,000 unique transformations included + $0.50 / 1,000 unique transformations / month |
-| Images Stored      | $5 / 100,000 images stored / month                                                         |
-| Images Delivered   | $1 / 100,000 images delivered / month                                                      |
-
-If you optimize an image stored outside of Images, then you will be billed only for Images Transformed.
-
-Alternatively, Images Stored and Images Delivered apply only to images that are stored in your Images bucket. When you optimize an image that is stored in Images, then this counts toward Images Delivered — not Images Transformed.
-
-## Metrics
-
-### Images Transformed
-
-A unique transformation is a request to transform an original image based on a set of [supported parameters](/images/transform-images/transform-via-url/#options). This metric is used only when optimizing images that are stored outside of Images.
-
-For example, if you transform `thumbnail.jpg` as 100x100, then this counts as 1 unique transformation. If you transform the same `thumbnail.jpg` as 200x200, then this counts as a separate unique transformation.
-
-You are billed for the number of unique transformations that are counted during each billing period.
-
-Unique transformations are counted over a 30-day sliding window. For example, if you request `width=100/thumbnail.jpg` on June 30, then this counts once for that billing period. If you request the same transformation on July 1, then this will not count as a billable request, since the same transformation was already requested within the last 30 days.
-
-The `format` parameter counts as only 1 billable transformation, even if multiple copies of an image are served. In other words, if `width=100,format=auto/thumbnail.jpg` is served to some users as AVIF and to others as WebP, then this counts as 1 unique transformation instead of 2.
-
-#### Example
-
-A retail website has 1,000 original product images that get served in 5 different sizes each month. This results in 5,000 unique transformations — or a cost of $2.50 per month.
-
-### Images Stored
-
-Storage in Images is available only with an Images Paid plan. You can purchase storage in increments of $5 for every 100,000 images stored per month.
-
-You can create predefined variants to specify how an image should be resized, such as `thumbnail` as 100x100 and `hero` as 1600x500.
-
-Only uploaded images count toward Images Stored; defining variants will not impact your storage limit.
-
-### Images Delivered
-
-For images that are stored in Images, you will incur $1 for every 100,000 images delivered per month. This metric does not include transformed images that are stored in remote sources.
-
-Every image requested by the browser counts as 1 billable request.
-
-#### Example
-
-A retail website has a product page that uses Images to serve 10 images. If the page was visited 10,000 times this month, then this results in 100,000 images delivered — or $1.00 in billable usage.
+Full information on long-term pricing of Containers is coming soon.

src/content/docs/containers/reference/pricing.mdx

@@ -157,6 +157,18 @@ wrangler init [<NAME>] [OPTIONS]
 
 ---
 
+## `containers`
+
+Interact with Cloudflare's Container Platform.
+
+:::note
+Currently `wrangler containers` does not exist. You will have to use `wrangler cloudchamber` instead.
+
+This will include several commands that will not work properly on your account if you are in the private beta.
+:::
+
+<Render file="wrangler-commands/containers" product="workers" />
+
 ## `d1`
 
 Interact with Cloudflare's D1 service.

src/content/docs/workers/wrangler/commands.mdx

@@ -0,0 +1,133 @@
+---
+{}
+---
+
+import { Render, AnchorHeading, Type, MetaInfo } from "~/components";
+
+<AnchorHeading title="`build`" slug="containers-build" depth={3} />
+
+Build a Container image from a Dockerfile.
+
+```txt
+wrangler containers build [PATH] [OPTIONS]
+```
+
+- `PATH` <Type text="string" /> <MetaInfo text="optional" />
+  - Path for the directory containing the Dockerfile to build.
+
+#### Options:
+
+- `-t, --tag` <Type text="string" /> <MetaInfo text="required" />
+  - Name and optionally a tag (format: "name:tag").
+- `--path-to-docker` <Type text="string" /> <MetaInfo text="optional" />
+  - Path to your docker binary if it's not on $PATH.
+  - Default: "docker"
+- `-p, --push` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Push the built image to Cloudflare's managed registry.
+  - Default: false
+- `--platform` <Type text="string" /> <MetaInfo text="optional" />
+  - Platform to build for. Defaults to the architecture supported by Workers (linux/amd64).
+  - Default: "linux/amd64"
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as clean JSON.
+  - Default: false
+
+<AnchorHeading title="`delete`" slug="containers-delete" depth={3} />
+
+Delete a Container (application).
+
+```txt
+wrangler containers delete <CONTAINER_ID> [OPTIONS]
+```
+
+- `CONTAINER_ID` <Type text="string" /> <MetaInfo text="required" />
+  - The ID of the Container to delete.
+- `-y, --skip-confirmation` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Skip deletion confirmation prompt.
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as JSON rather than a table.
+
+<AnchorHeading title="`images`" slug="containers-images" depth={3} />
+
+Perform operations on images in your containers registry.
+
+<AnchorHeading title="`images list`" slug="containers-images-list" depth={4} />
+
+List images in your containers registry.
+
+```txt
+wrangler containers images list [OPTIONS]
+```
+
+#### Options:
+
+- `--filter` <Type text="string" /> <MetaInfo text="optional" />
+  - Regex to filter results.
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as clean JSON.
+  - Default: false
+
+<AnchorHeading
+	title="`images delete`"
+	slug="containers-images-delete"
+	depth={4}
+/>
+
+Remove an image from your containers registry.
+
+```txt
+wrangler containers images delete [IMAGE] [OPTIONS]
+```
+
+- `IMAGE` <Type text="string" /> <MetaInfo text="required" />
+  - Image to delete.
+
+#### Options:
+
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as clean JSON.
+  - Default: false
+
+<AnchorHeading title="`info`" slug="containers-info" depth={3} />
+
+Get information about a specific Container, including top-level details and a list of instances.
+
+```txt
+wrangler containers info <CONTAINER_ID> [OPTIONS]
+```
+
+- `CONTAINER_ID` <Type text="string" /> <MetaInfo text="required" />
+  - The ID of the Container to get information about.
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as JSON rather than a table.
+
+<AnchorHeading title="`list`" slug="containers-list" depth={3} />
+
+List the Containers in your account.
+
+```txt
+wrangler containers list [OPTIONS]
+```
+
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as JSON rather than a table.
+
+<AnchorHeading title="`push`" slug="containers-push" depth={3} />
+
+Push a tagged image to a Cloudflare managed registry, which is automatically integrated with your account.
+
+```txt
+wrangler containers push [TAG] [OPTIONS]
+```
+
+- `TAG` <Type text="string" /> <MetaInfo text="required" />
+  - The name and tag of the container image to push.
+
+#### Options:
+
+- `--path-to-docker` <Type text="string" /> <MetaInfo text="optional" />
+  - Path to your docker binary if it's not on $PATH.
+  - Default: "docker"
+- `--json` <Type text="boolean" /> <MetaInfo text="optional" />
+  - Return output as clean JSON.
+  - Default: false