Files
David Karlsson 1773367159 Sync sbx CLI reference from release/v0.51 (#26514)
Vendor the checked-in CLI YAML from Docker Sandboxes release/v0.51 at
7d55286de0c7. This updates command help, adds `sbx policy check http`,
and replaces seven agent-specific create pages with redirects to `sbx
create`.

Validation: full site build with Hugo 0.169.0; upstream byte-for-byte
comparison; all 115 command pages, reference links, and seven redirects
checked; template formatting and whitespace checks passed.
2026-11-04 10:10:52 +01:00

43 lines
1.5 KiB
YAML

name: sbx kit pull
synopsis: Pull a kit artifact from an OCI registry
experimental: true
description: |-
Pull a kit artifact from an OCI registry and save its payload to a file.
Use a registry/repo:tag or registry/repo@sha256:digest reference.
The output extension follows the resolved artifact format: .zip for v1,
or .tar.gz for v2. Use --output to choose the file path.
For Docker Hub, the sbx login session takes priority. Other registries use
secrets set with sbx secret set --registry. Both fall back to Docker credentials.
The registry must support HTTPS.
usage: sbx kit pull REFERENCE [flags]
options:
- name: help
shorthand: h
default_value: "false"
usage: help for pull
- name: output
shorthand: o
usage: 'Output file path (default: derived from reference + format)'
inherited_options:
- name: cloud
default_value: "false"
usage: |
Dispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
- name: debug
shorthand: D
default_value: "false"
usage: Enable debug logging
- name: no-input
default_value: "false"
usage: |
Never prompt; commands that need an answer fail with the command to run instead
example: |4-
sbx kit pull ghcr.io/myorg/my-kit:1.0
# Choose where to save the payload
sbx kit pull ghcr.io/myorg/my-kit:1.0 --output my-kit.tar.gz
see_also:
- sbx kit - (Experimental) Manage kit artifacts