From 72573a0e8e9abaf9034fddb05cf2864019037213 Mon Sep 17 00:00:00 2001 From: emily-shen Date: Mon, 20 Apr 2026 14:54:46 +0100 Subject: [PATCH 1/3] Adds docs for container rollout none option --- src/content/docs/containers/get-started.mdx | 11 +++++++++++ src/content/docs/sandbox/configuration/wrangler.mdx | 13 +++++++++++++ .../docs/workers/wrangler/commands/workers.mdx | 6 ++++-- 3 files changed, 28 insertions(+), 2 deletions(-) diff --git a/src/content/docs/containers/get-started.mdx b/src/content/docs/containers/get-started.mdx index a010264ca26..5eab1aabb5d 100644 --- a/src/content/docs/containers/get-started.mdx +++ b/src/content/docs/containers/get-started.mdx @@ -22,6 +22,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. */} +### 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`](/workers/wrangler/commands/workers/#deploy) to the deploy command: + + + +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. {/* FUTURE CHANGE: Link to docs on alternative build/push options */} ## Deploy your first Container diff --git a/src/content/docs/sandbox/configuration/wrangler.mdx b/src/content/docs/sandbox/configuration/wrangler.mdx index 32a4cf0ec33..874c693e9cb 100644 --- a/src/content/docs/sandbox/configuration/wrangler.mdx +++ b/src/content/docs/sandbox/configuration/wrangler.mdx @@ -52,6 +52,19 @@ 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`](/workers/wrangler/commands/workers/#deploy) to the deploy command: + + + +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. + + ## Backup storage To use the [backup and restore API](/sandbox/api/backups/), you need an R2 bucket binding and presigned URL credentials. The container uploads and downloads backup archives directly to/from R2 using presigned URLs, which requires R2 API token credentials. diff --git a/src/content/docs/workers/wrangler/commands/workers.mdx b/src/content/docs/workers/wrangler/commands/workers.mdx index 18aee6ebdbe..fe605729137 100644 --- a/src/content/docs/workers/wrangler/commands/workers.mdx +++ b/src/content/docs/workers/wrangler/commands/workers.mdx @@ -225,8 +225,10 @@ 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. +- `--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. + - If set to `none`, the container image will not be updated, allowing you to deploy Worker code changes without rebuilding the container image. - Defaults to `gradual`, where the default rollout is 10% then 100% of instances. - `--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. From b14e61e451d5343ef96c050e605565b53d74e9bc Mon Sep 17 00:00:00 2001 From: emily-shen <69125074+emily-shen@users.noreply.github.com> Date: Mon, 20 Apr 2026 15:04:36 +0100 Subject: [PATCH 2/3] Update src/content/docs/workers/wrangler/commands/workers.mdx Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- src/content/docs/workers/wrangler/commands/workers.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/workers/wrangler/commands/workers.mdx b/src/content/docs/workers/wrangler/commands/workers.mdx index fe605729137..41414ade97e 100644 --- a/src/content/docs/workers/wrangler/commands/workers.mdx +++ b/src/content/docs/workers/wrangler/commands/workers.mdx @@ -227,8 +227,8 @@ None of the options for this command are required. Also, many can be set in your - 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. - - If set to `none`, the container image will not be updated, allowing you to deploy Worker code changes without rebuilding the container image. + - 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. + - If set to `none`, the container image will not be updated, allowing you to deploy Worker code changes without rebuilding the container image. - Defaults to `gradual`, where the default rollout is 10% then 100% of instances. - `--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. From 49de3eb075e24d1344456f7955df4c63ebe9fa1b Mon Sep 17 00:00:00 2001 From: emily-shen Date: Mon, 20 Apr 2026 15:05:22 +0100 Subject: [PATCH 3/3] fixup import --- src/content/docs/sandbox/configuration/wrangler.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/sandbox/configuration/wrangler.mdx b/src/content/docs/sandbox/configuration/wrangler.mdx index 874c693e9cb..143df00d3fc 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