| > Mac users using a hypervisor? Windows using running Linux in a Virtualbox? Vagrant works natively on Macs and Windows, unlike Docker. There is zero reason to run it inside an already virtualised environment on those machines. > I am talking about rebuilding the Vagrant image every time you change it You know you don't need to destroy the vagrant environment to re-run the provisioning scripts, if something changes.. right? > Sure, once it's written (by someone who has to spend a fair amount of elapsed time doing trial-and-error tweaks) With the minor exception of a few Vagrant specific optimisations (a `vagrant` user with the predefined SSH key & passwordless sudo, for example) during base-box building, literally nothing in a Vagrant provisioning environment needs to be specific to Vagrant. Also - if you're building base-boxes, it's probably worthwhile forking an existing project that targets your Distro/OS of choice and customising from there. > On the other hand, that too can result in people using stale images over time as the configuration drifts. Why? If it's a small change, just set the provisioner to `run: "always"` and it will run on every up. Assuming the changes (i.e. new/updated deps, or config files being copied) are small, it'll be almost instantaneous. From everything you've said, I'm very curious how you use Vagrant (if at all). It isn't intended to be used like Docker, where you package up an entire image completely ready to use with 0 cycles needed to configure anything, and an update means a new image. |