Share feedback
Answers are generated based on the documentation.

sbx kit pull

DescriptionPull a kit artifact from an OCI registry
Usagesbx kit pull REFERENCE [flags]

Experimental

This command is experimental.

Experimental features are intended for testing and feedback as their functionality or design may change between releases without warning or can be removed entirely in a future release.

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.

Options

OptionDefaultDescription
-o, --outputOutput file path (default: derived from reference + format)

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging

Examples

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