Skip to main content

msb pull

Pre-pull an image to the local cache. Layers are fetched in parallel with per-layer progress bars. Once cached, layers are content-addressable and deduplicated, so shared layers across images are only stored once.
Expanded form: msb image pull.
Pre-pulling is useful when you want sandbox creation to be instant. Without a pre-pull, the first Sandbox.create with a new image will block on the download.

msb load

Load a Docker image archive or OCI Image Layout archive into the local microsandbox cache.
Expanded form: msb image load.

msb save

Save one or more cached images as a Docker-compatible archive or OCI Image Layout archive.
Expanded form: msb image save. msb save re-exports images from microsandbox’s EROFS cache. The saved archive is semantically equivalent, but it is not a byte-for-byte copy of the originally pulled image. Manifest digest and layer digests can change because layer tar streams are regenerated.

msb images

List images in the local cache.
Expanded form: msb image ls.

msb image inspect

Show detailed metadata for a cached image (manifest, layers, config).

msb rmi

Remove one or more cached images and their layers (layers shared with other images are kept).
Expanded form: msb image rm.

msb image prune

Remove cached images that are not used by any sandbox or indexed snapshot, then clean up dangling image artifacts.
Prune never removes images used by existing sandboxes or indexed snapshots. It also cleans up image metadata, unreachable manifests, orphaned layers, layer EROFS artifacts, fsmeta EROFS artifacts, and VMDK descriptor artifacts. Use msb rmi --force when you want to remove a specific image even though it is still referenced by a sandbox.

msb registry

Manage registry authentication.
msb registry login flags: msb registry login stores the secret in the OS credential store (for example Keychain, Credential Manager, or Secret Service) and writes only metadata to ~/.microsandbox/config.json. For CI or other headless environments, configure registries.hosts.<host>.auth in ~/.microsandbox/config.json with password_env. Advanced host setups can also use secret_name to point at a file-backed secret under ~/.microsandbox/secrets/registries/. When pulling from a registry, microsandbox resolves auth in this order:
  1. Explicit SDK auth (.registry(|r| r.auth(...)))
  2. OS credential store
  3. registries.hosts.<host>.auth config
  4. Docker credential store/config
  5. Anonymous