whenever you vagrant up the plugin will upgrade the guest additions for you when a.
#VAGRANT UPGRADE INSTALL#
In my case, I routinely build, destroy and rebuild Vagrant machines since I build them mainly for deployment and provisioning testing before moving onto a more permanent environment. Overview Install VirtualBox and Vagrant Clone the Aurora repository. Cases where you would do something like this would be where you have provisioning scripts in place to configure the Vagrant machine on creation and even if you deploy code to the box from some other place-like a GitHub repository-so your Vagrant machine is just a platform of some type. If a Vagrant environment is already running, you'll have to destroy and re create it to acquire the new updates in the box. This will not magically update running Vagrant environments. This will download and install the new box. Using the example above, if you know you can replicate your work on that box, then blowing away that Vagrant machine is fine. 2 Answers Sorted by: 61 From the Vagrant docs: Finally, you can update boxes with vagrant box update. The main benefit of vagrant box update is for creating new Vagrant machines. Upgrading Ubuntu 12 to 14 on an existing virtual machine. In a case like that, upgrading Ubuntu via apt-get is the safest bet since it will assure you that any work you have done on that box after it was built will still be there when the upgrade completes. Meaning any already existing Vagrant machines will not be upgraded.īut if you do an update via apt-get within the Ubuntu Vagrant machine, then your already existing machine will be upgraded.įor example, let’s say you do tons of development on one of those boxes and have tons of work on that Vagrant machine that is not easily replicated. When you do vagrant box update all it does is update the local box a Vagrant machine was initially built with.
0 kommentar(er)
