I've the problem that my home directory is actually located on a remote server and with ~/.vagrant.d sitting on that server, the performance of vagrant decreases heavily (and file-server backup size increases).
So is there any way to move at least ~/vagrant.d/boxes out of the home directory?
Cheers.
If on Windows, this directory is located at C:\Users\YourUsername\. vagrant. d , where YourUsername is the username of your local user. When debugging, the Vagrant support team may ask you to remove this directory.
Fortunately, vagrant provides an environment variable called VAGRANT_HOME by which you can set vagrant home. To make it permanent, add this to your ~/. bash_profile (for login shell). VAGRANT_HOME can be set to change the directory where Vagrant stores global state.
By default, Vagrant stores its boxes after downloading in the directory defined by VAGRANT_HOME environment variable. As a result, On Mac OS X and Linux: ~/. vagrant.
By default Vagrant uses ~/.vagrant.d
. Fortunately, vagrant provides an environment variable called VAGRANT_HOME
by which you can set vagrant home.
Just do the following to change the vagrant home (this only works in the current session)
export VAGRANT_HOME=/path/to/vagrant
To make it permanent, add this to your ~/.bash_profile
(for login shell).
Update: VAGRANT_HOME
has been added to the documentation - Environmental Variables
VAGRANT_HOME
can be set to change the directory where Vagrant stores global state. By default, this is set to~/.vagrant.d
. The Vagrant home directory is where things such as boxes are stored, so it can actually become quite large on disk.
VAGRANT_HOME
does not work well in my Windows 8.1. It worked for me when I changed the file
D:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.5.3\lib\vagrant\environment.rb
on line 117 to
@home_path = Util::Platform.fs_real_path("D:/vagrant/home/")
like Steve H said and it works fine.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With