Does Vagrant cache base boxes from the same HTTP URL?

[Eric Riebling]

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*

[Alvaro Miranda Aguilera]

Hello,

If you use user/box and the index of the box is on Atlas, you will use
versioning.

The versioning is something that does exist on the index.

The index basically is what tells vagrant (the client), for 0.0.1 use
box_0.0.1.box, etc

There are some blog post in the internet that show how to create the
json files to have versioning.

Can you share some information? are you or you will be using atlas?

if not, then you should implement the versioning on your side.

ie. HAve a look a this:
https://atlas.hashicorp.com/hashicorp/boxes/precise64.json

> --
> 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 vagrant-up+...@googlegroups.com.
> 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.

[dragon788]

If you are using a versioned box and you don't disable the update prompt, every time the user runs 'vagrant up' they will get a prompt that a newer version of the box is available. Sometimes this is desirable if you are creating "phoenix" boxes that don't actually contain any data that needs to persist then you will be OK with updating the box, since the older version is available cached locally. If you on the other hand allow developers to create "snowflake" boxes with their own development environment, then annoying them with the update warning or having them accidently lose their progress by following the directions of a 'vagrant box update' followed by a 'vagrant destroy' and 'vagrant up' will make them even more unhappy.