`vectron stack provision`

Main command

vectron stack provision

This command expects an existing vectron.stack.toml. It:

• validates vectron.stack.toml
• runs stack-specific preflight logic
• resolves implicit plugin dependencies such as kubernetes selecting docker_registry
• creates .vectron_stack/
• generates a derived vectron.toml
• provisions plugin-specific assets where required

The generated runtime config disables liveness probes by default to avoid noisy local stack logs. Set [supervision] liveness_probes = true in vectron.stack.toml to opt back in.

Useful flags

• --dry-run: print what would happen without making changes
• --force: allow deleting a non-empty .vectron_stack/data directory where supported
• --only: restrict execution to selected plugins
• --skip: exclude selected plugins

--skip docker_registry is invalid when kubernetes remains selected, because Kubernetes drivers use the generated registry endpoint for local stack images.

When Kubernetes is selected, vectron stack provision temporarily starts docker_registry before cluster provisioning and restores the registry container to its previous running or stopped state afterward.

Safe workflow

vectron stack init
vectron stack check
vectron stack provision --dry-run
vectron stack provision
vectron start

Generated files

The stack system writes generated state under .vectron_stack/, including the generated configuration used by the normal runtime.