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
 <Render product="containers" file="docker-setup" />
 
 {/* 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:
+
+<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
diff --git a/src/content/docs/sandbox/configuration/wrangler.mdx b/src/content/docs/sandbox/configuration/wrangler.mdx
index 32a4cf0ec33..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
 
@@ -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.
diff --git a/src/content/docs/workers/wrangler/commands/workers.mdx b/src/content/docs/workers/wrangler/commands/workers.mdx
index 18aee6ebdbe..41414ade97e 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` <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.