sbx kit validate
| Description | Validate a kit artifact |
|---|---|
| Usage | sbx kit validate 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
Validate that a directory or ZIP file is a valid kit artifact.
The reference can be a local directory, ZIP file path, or git repository.
A kit that declares required arguments is invalid until they are supplied, so pass the same --kit-arg values you would pass to sbx create.
--offline skips the daemon-backed kit policy (kit.allowedSources, kit.allowLocalKits, kit.requireSignature) so the command needs neither sandboxd nor a signed-in session; it only accepts a local directory or ZIP reference, since those are the only ones this check applies to.
Options
| Option | Default | Description |
|---|---|---|
--format | Output format: table, json or yaml | |
--json | Output in JSON format | |
--kit-arg | experimental Value for an argument the kit declares, as name=value for every kit or kit.name=value for one (can be repeated) | |
--kit-args-file | experimental File of name=value kit arguments, one per line (can be repeated); --kit-arg overrides | |
--offline | Skip the daemon-backed kit policy check; local directory or ZIP references only |
Global options
| Option | Default | Description |
|---|---|---|
--cloud | 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) | |
-D, --debug | Enable debug logging | |
--no-input | Never prompt; commands that need an answer fail with the command to run instead |
Examples
sbx kit validate ./my-kit
sbx kit validate ./my-kit.zip
# Supply the arguments a kit declares
sbx kit validate ./my-kit --kit-arg region=eu
# Validate without sandboxd running or a Docker sign-in
sbx kit validate ./my-kit --offline