You mean to tell me that creating a new VM from a base box on a given URL is not guaranteed to get what is on the server?
I know this might be clever, and save time, but what if you are developing that base box and want to rely on new VMs getting the latest version each time? You know, the one specified by config.vm.box when doing "vagrant up"? I guess versioning is required, eh. Damn I wish I knew about this sooner. The documentation and design behind the "vagrant box" commands don't make this especially clear. Cacheing of base boxes seems rather a secret to the first time user. I guess the design assumption is that base boxes deployed on a URL will never change? *HEADDESK* -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6552cee3-a9e2-4c6b-b636-4a50bd37eb2b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
