For example following image illustrate two VM running under VirtualBox Node_default_1387087098 and Blogs_default_1386384681 If you are using VirtualBox as provider you can see a list of virtual machine with their specific machine. Also repackaging allows me to work offline as no provisioning is required.įirst step is to get id or specific name of VM from your Vagrant provider. Once install/update is finished, sometime I prefer to repackage updated virtual machine as a new base box to avoid repeating the install and update process.

Then using either Puppet provisioner or apt-get I normally install/update required packages and libraries in my VM.

With help of a Vagrant provider vagrant up will create a virtual machine (VM) using specified base box. Any form of box add that works seems to set the version as 0.Typically my Vagrant workflow starts with a official base box provided by Ubuntu. Please remove the version constraint and try again.īut I'm not trying to constrain what I'm adding I'm trying to specify. You specified a box version constraint with a direct box file path.īox version constraints only work with boxes from Vagrant Cloud or aĬustom box host. Attempting to specify box-version anyway results in:

Vagrant box add appears to have a option -box-version, but this is for constraining the version of a box being downloaded, not for specifying the version of a box being added. In other words, I'd like to run vagrant box add, while specifying a newer version and a local file. However, when I'm developing new versions of my box locally, I don't want to have to go through an upload/download cycle every time I want to upgrade the version of the box loaded in Vagrant. I'm using versioned boxes, but not using Vagrant Cloud (I have a custom box host).

Box vagrant