Run: 'always' vs 'once' — Choosing the Right Provisioner Strategy for Retry‑Safe, Non‑Idempotent Scripts
When a Vagrant machine fails to provision due to a transient network glitch or a synced‑folder mount error, the provisioner may be retried automatically. If the provisioner is configured with run: 'always' , Vagrant will execute it on every retry, potentially causing duplicate writes such as appending timestamps or installing packages twice. Setting run: 'on