tare precheck

Validate that every container image a TARS install or upgrade needs is
present and complete in the target registry, before running the deploy.

For each image, precheck verifies the repository and tag (or digest) exist,
the manifest is retrievable, and the required platform(s) are available. It
fails with a per-image report identifying exactly what is missing.

This is the same check 'tare install' and 'tare upgrade' run automatically;
run it standalone to validate a registry mirror after an image sync, or to
debug an install that failed pulling images.

Examples:
  # Validate the default Tetrate registry
  tare precheck identity.json

  # Validate a private mirror you synced images into
  tare precheck identity.json --image-registry acme.registry.com

  # Require multiple platforms
  tare precheck identity.json --platform linux/amd64 --platform linux/arm64

Usage:
  tare precheck <identity-file> [flags]

Flags:
      --image-registry string   Registry to validate. Defaults to REGISTRY_URL env, then registry.tetrate.ai.
      --platform stringArray    Required platform(s) every image must provide, repeatable (e.g. --platform linux/amd64). Default: linux/amd64.
      --progress string         Progress display: auto|tty|plain|none. (default "auto")

Global Flags:
  -q, --quiet     Suppress progress output; only errors and the final summary go to stderr
  -v, --verbose   Verbose output: plain-mode progress lines plus full per-blob chunk logs to stderr