From 52d5d5c274aeda8e13882c8c076eaddbbdca9d33 Mon Sep 17 00:00:00 2001 From: Mike Nomitch Date: Mon, 23 Feb 2026 16:24:06 -0800 Subject: [PATCH 1/2] Adds docs for container rollout none option --- src/content/docs/containers/get-started.mdx | 13 +++++++++++-- .../docs/sandbox/configuration/wrangler.mdx | 14 +++++++++++++- src/content/docs/workers/wrangler/commands.mdx | 8 +++++--- 3 files changed, 29 insertions(+), 6 deletions(-) diff --git a/src/content/docs/containers/get-started.mdx b/src/content/docs/containers/get-started.mdx index 5849c82fc76..d5cf7078a74 100644 --- a/src/content/docs/containers/get-started.mdx +++ b/src/content/docs/containers/get-started.mdx @@ -21,8 +21,17 @@ In this guide, we will build and push a container image alongside your Worker co -{/* FUTURE CHANGE: Add some image you can use if you don't have Docker running. */} -{/* FUTURE CHANGE: Link to docs on alternative build/push options */} +### Deploy without Docker + +If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass `--containers-rollout=none` to the deploy command: + + + +This skips the container image build and push steps, deploying your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option. ## Deploy your first Container diff --git a/src/content/docs/sandbox/configuration/wrangler.mdx b/src/content/docs/sandbox/configuration/wrangler.mdx index 12baf25c8c2..c83967d68bd 100644 --- a/src/content/docs/sandbox/configuration/wrangler.mdx +++ b/src/content/docs/sandbox/configuration/wrangler.mdx @@ -5,7 +5,7 @@ sidebar: order: 1 --- -import { WranglerConfig } from "~/components"; +import { WranglerConfig, PackageManagers } from "~/components"; ## Minimal configuration @@ -52,6 +52,18 @@ The Sandbox SDK is built on Cloudflare Containers. Your configuration requires t The minimal configuration shown above includes all required settings. For detailed configuration options, refer to the [Containers configuration documentation](/workers/wrangler/configuration/#containers). +## Deploy without Docker + +If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass `--containers-rollout=none` to the deploy command: + + + +This skips the container image build and push steps, deploying your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option. + ## Troubleshooting ### Binding not found diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx index e697000ce04..edbd961f00b 100644 --- a/src/content/docs/workers/wrangler/commands.mdx +++ b/src/content/docs/workers/wrangler/commands.mdx @@ -336,9 +336,11 @@ None of the options for this command are required. Also, many can be set in your - Specify the [Workers for Platforms dispatch namespace](/cloudflare-for-platforms/workers-for-platforms/how-workers-for-platforms-works/#dispatch-namespace) to upload this Worker to. - `--metafile` - Specify a file to write the build metadata from esbuild to. If flag is used without a path string, this defaults to `bundle-meta.json` inside the directory specified by `--outdir`. This can be useful for understanding the bundle size. -- `--containers-rollout` - - Specify the [rollout strategy](/containers/faq#how-do-container-updates-and-rollouts-work) for [Containers](/containers) associated with the Worker. If set to `immediate`, 100% of container instances will be updated in one rollout step, overriding any configuration in `rollout_step_percentage`. Note that `rollout_active_grace_period`, if configured, still applies. - - Defaults to `gradual`, where the default rollout is 10% then 100% of instances. +- `--containers-rollout` + - Specify the [rollout strategy](/containers/faq#how-do-container-updates-and-rollouts-work) for [Containers](/containers) associated with the Worker. + - `gradual` (default) — Rolls out to 10% then 100% of instances. + - `immediate` — Rolls out to 100% of container instances in one step, overriding any configuration in `rollout_step_percentage`. Note that `rollout_active_grace_period`, if configured, still applies. + - `none` — Skips building and pushing a new container image. Use this when you do not have Docker running locally but still want to deploy Worker code changes. The deployment uses the existing container image from a previous deploy. - `--strict` - Turns on strict mode for the deployment command, meaning that the command will be more defensive and prevent deployments which could introduce potential issues. In particular, this mode prevents deployments if the deployment would potentially override remote settings in non-interactive environments. - `--tag` From ed2cde14ae75dc65f3fa8d84def25ebc04f487fb Mon Sep 17 00:00:00 2001 From: Mike Nomitch Date: Mon, 6 Apr 2026 13:07:01 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com> --- src/content/docs/containers/get-started.mdx | 4 ++-- src/content/docs/sandbox/configuration/wrangler.mdx | 4 ++-- src/content/docs/workers/wrangler/commands.mdx | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/containers/get-started.mdx b/src/content/docs/containers/get-started.mdx index d5cf7078a74..2b58876ffa7 100644 --- a/src/content/docs/containers/get-started.mdx +++ b/src/content/docs/containers/get-started.mdx @@ -23,7 +23,7 @@ In this guide, we will build and push a container image alongside your Worker co ### Deploy without Docker -If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass `--containers-rollout=none` to the deploy command: +If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass [`--containers-rollout=none`](/workers/wrangler/commands/#deploy) to the deploy command: -This skips the container image build and push steps, deploying your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option. +This skips the container image build and push steps and deploys your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option. ## Deploy your first Container diff --git a/src/content/docs/sandbox/configuration/wrangler.mdx b/src/content/docs/sandbox/configuration/wrangler.mdx index c83967d68bd..8c141c41a9a 100644 --- a/src/content/docs/sandbox/configuration/wrangler.mdx +++ b/src/content/docs/sandbox/configuration/wrangler.mdx @@ -54,7 +54,7 @@ The minimal configuration shown above includes all required settings. For detail ## Deploy without Docker -If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass `--containers-rollout=none` to the deploy command: +If you do not have Docker running locally but want to deploy Worker code changes without rebuilding the container image, pass [`--containers-rollout=none`](/workers/wrangler/commands/#deploy) to the deploy command: -This skips the container image build and push steps, deploying your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option. +This skips the container image build and push steps and deploys your Worker code while reusing the existing container image from a previous deployment. You must have deployed the container at least once with Docker before using this option. ## Troubleshooting diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx index edbd961f00b..0b31e25dbbd 100644 --- a/src/content/docs/workers/wrangler/commands.mdx +++ b/src/content/docs/workers/wrangler/commands.mdx @@ -340,7 +340,7 @@ None of the options for this command are required. Also, many can be set in your - Specify the [rollout strategy](/containers/faq#how-do-container-updates-and-rollouts-work) for [Containers](/containers) associated with the Worker. - `gradual` (default) — Rolls out to 10% then 100% of instances. - `immediate` — Rolls out to 100% of container instances in one step, overriding any configuration in `rollout_step_percentage`. Note that `rollout_active_grace_period`, if configured, still applies. - - `none` — Skips building and pushing a new container image. Use this when you do not have Docker running locally but still want to deploy Worker code changes. The deployment uses the existing container image from a previous deploy. + - `none` — Skips building and pushing a new container image. Use this when you do not have Docker running locally but still want to deploy Worker code changes. The deployment uses the existing container image from a previous deployment. - `--strict` - Turns on strict mode for the deployment command, meaning that the command will be more defensive and prevent deployments which could introduce potential issues. In particular, this mode prevents deployments if the deployment would potentially override remote settings in non-interactive environments. - `--tag`