autonomy registry sync

Re-seed a peer edge registry from this one (edge-to-edge, delta via skopeo)

Synopsis

Replicates a set of repos from one edge registry to a peer — a seeded edge node
re-seeds a neighbour. It builds one seed per repo (from A/<repo> to B/<repo>) and
composes 'registry seed-catalog'. The incremental delta is provided naturally by
skopeo, which skips blobs the destination already holds (both ends dedupe by
content digest), so only changed layers cross the wire.

Verification is fail-closed exactly like 'registry seed': pass --pub-key, or
explicitly --skip-verify. Each repo is verified against the same key.

Usage

autonomy registry sync --from-registry <A> --to-registry <B> --repos <repo:tag,...> [flags]

Examples

autonomy registry sync \
      --from-registry edge-a.local:5000 --to-registry edge-b.local:5000 \
      --repos robot-behavior:v1,fleet/nav-stack:v2 \
      --pub-key ./cosign.pub --out ./sync

  autonomy registry sync --from-registry a:5000 --to-registry b:5000 \
      --repos demo:v1 --allow-insecure-registry --skip-verify

Options

      --allow-insecure-registry   permit plain-HTTP registries (e.g. localhost)
      --copy-policy               also replicate each repo's lock/policy sidecars
      --from-registry string      source registry host (e.g. edge-a.local:5000); required
      --keep-going                attempt every repo and report failures (still exits non-zero if any failed)
      --out string                directory for the catalog roll-up + per-repo subdirs (default ".")
      --pub-key string            cosign public key (SPKI PEM) verifying every synced repo
      --repos strings             repo[:tag] paths to replicate (comma-separated or repeated); required
      --skip-verify               bypass verification for all repos (fail-open; dev only)
      --to-registry string        destination peer registry host (e.g. edge-b.local:5000); required

See also

• autonomy registry — Seed and govern OCI registries for edge / air-gapped deployments