centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-03-27 14:28:47 +07:00
Code Issues Packages Projects Releases Wiki Activity

sandboxes: fix incorrect descriptions for --pull-template

Browse Source 
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson
2026-02-19 15:15:59 +01:00
parent 541607aa12
commit 9cd0887783
2 changed files with 17 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/manuals/ai/sandboxes/migration.md
View File

@@ -120,15 +120,13 @@ template.
4. Create a new sandbox with your template:
```console
$ docker sandbox create --template my-sandbox-template:v1 \
--pull-template=never \
claude ~/project
$ docker sandbox create --template my-sandbox-template:v1 claude ~/project
```
> [!NOTE]
> The `--pull-template` flag was introduced in Docker Desktop 4.61 (Sandbox
> version 0.12). For Docker Desktop 4.58–4.60, substitute
> `--pull-template=never` with `--load-local-template`.
> version 0.12). On Docker Desktop 4.58–4.60, use `--load-local-template`
> to use a locally-built template image.
5. Run the sandbox:

27
content/manuals/ai/sandboxes/templates.md
View File

@@ -68,11 +68,11 @@ $ docker build -t my-template:v1 .
Use it directly from your local Docker daemon:
```console
$ docker sandbox run --pull-template never -t my-template:v1 claude [PATH]
$ docker sandbox run -t my-template:v1 claude [PATH]
```
The `--pull-template never` flag tells the sandbox to use local template
images.
The default `--pull-template missing` policy finds the image in your local
Docker daemon without pulling from a registry.
To share the template with others, push it to a registry:
@@ -92,19 +92,20 @@ Docker Sandboxes caches template images to speed up sandbox creation. The
- `--pull-template missing` (default)
Pull the image only if it's not already cached locally. First sandbox
creation automatically pulls the image, and subsequent sandboxes are created
quickly because the image is cached.
Use the local image if present, otherwise pull from the registry. Works for
both locally-built images and registry images. On first use, registry images
are pulled and cached; subsequent sandboxes reuse the cache.
- `--pull-template always`
Always pull the image from the registry before creating the sandbox, even if
it's cached. Slower than `missing` but guarantees freshness.
Always pull the latest image from the registry and update the host cache.
The VM uses the refreshed cache. Slower than `missing` but guarantees the
sandbox uses the latest version. Requires a registry image.
- `--pull-template never`
Use only cached images. Never pull from a registry. Fails if the image isn't
in the cache.
Never use the host cache. The sandbox VM pulls the image directly from the
registry on every startup. Requires a registry image.
The cache stores template images separately from your host Docker daemon's
images. Cached images persist across sandbox creation and deletion, but are
@@ -130,11 +131,11 @@ $ docker sandbox save claude-project my-template:v1
✓ Saved sandbox as my-template:v1
```
This saves the image to your local Docker daemon. Use `--pull-template never`
to create new sandboxes from it:
This saves the image to your local Docker daemon. The default pull policy finds
the image locally:
```console
$ docker sandbox run --pull-template never -t my-template:v1 claude ~/other-project
$ docker sandbox run -t my-template:v1 claude ~/other-project
```
To save as a tar file instead (for example, to transfer to another machine):