Skip to content

Adds docs for container rollout none option #30089

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
emily-shen wants to merge 3 commits into from
Closed

Adds docs for container rollout none option #30089

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
72573a0
Adds docs for container rollout none option
emily-shen Apr 20, 2026
b14e61e
Update src/content/docs/workers/wrangler/commands/workers.mdx
emily-shen Apr 20, 2026
49de3eb
fixup import
emily-shen Apr 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/content/docs/containers/get-started.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,17 @@ In this guide, we will build and push a container image alongside your Worker co
<Render product="containers" file="docker-setup" />

{/* FUTURE CHANGE: Add some image you can use if you don't have Docker running. */}
### Deploy without Docker

@nikitassharma nikitassharma Apr 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using an image uri instead of a Dockerfile ref will also allow deploy without docker iirc which would also allow deploying containers changes without requiring docker. Not sure if that's worth calling out here


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:

<PackageManagers
type="exec"
pkg="wrangler"
args="deploy --containers-rollout=none"
/>

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
Expand Down
15 changes: 14 additions & 1 deletion src/content/docs/sandbox/configuration/wrangler.mdx
View file
Open in desktop
Comment thread
emily-shen marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 1
---

import { WranglerConfig } from "~/components";
import { WranglerConfig, PackageManagers } from "~/components";

## Minimal configuration

Expand Down Expand Up @@ -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:

<PackageManagers
type="exec"
pkg="wrangler"
args="deploy --containers-rollout=none"
/>

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.
Expand Down
6 changes: 4 additions & 2 deletions src/content/docs/workers/wrangler/commands/workers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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` <Type text="string" /> <MetaInfo text="optional" />
- 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` <Type text="immediate | gradual" /> <MetaInfo text="optional" />
- 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` <Type text="immediate | gradual | none" /> <MetaInfo text="optional" />
- 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` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
- 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.
Expand Down