Vagrant.d outside of the home folder

vagrant

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.

Best Answer

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.

Related Solutions

Using vagrant to run virtual machines with desktop environment

I just got this working with basically three steps. The advice from askubuntu.com didn't quite work for me, so try this simplified version:

Get a basic Ubuntu image working. You should be able to boot it and vagrant ssh.
Next, enable the VirtualBox display, which is off by default. Halt the VM and uncomment these lines in Vagrantfile:
```
config.vm.provider :virtualbox do |vb|
  vb.gui = true
end
```
Boot the VM and observe the new display window. Now you just need to install and start xfce4. Use vagrant ssh and:
```
sudo apt-get install xfce4
sudo startxfce4&
```

If this is the first time you're running this Ubuntu environment, you'll need to run the following command before installing xfce4:

sudo apt-get update

That's it, you should be landed in a xfce4 session.

Update: For a better experience, I recommend these improvements:

Don't start the GUI as root. You really want to stay the vagrant user. To do this you need to permit anyone to start the GUI: sudo vim /etc/X11/Xwrapper.config and edit it to allowed_users=anybody.
Next, install the VirtualBox guest tools before starting the GUI. This will give you a healthy screen resolution, integrated mouse, etc.
```
$ sudo apt-get install -y xfce4 virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11
$ sudo VBoxClient-all
```
Only now should you start the GUI as the vagrant user, with $ startxfce4&.

Update 2: Tried this today and the VBoxClient-all script isn't always installed. If it's missing, you can replace with the equivalent:

sudo VBoxClient --clipboard
sudo VBoxClient --draganddrop
sudo VBoxClient --display
sudo VBoxClient --checkhostversion
sudo VBoxClient --seamless

Ruby-on-rails – Tell Vagrant the ip of the host machine

According to this, you can reach the host through the VM's default gateway.

Running netstat -rn on the guest should give you the relevant info, on my machine changing your code above to the following looks like it would get things going for you:

# database.yml
development:
  host: <%= `netstat -rn | grep "^0.0.0.0 " | cut -d " " -f10` %>

Best Answer

Related Solutions

Using vagrant to run virtual machines with desktop environment

Ruby-on-rails – Tell Vagrant the ip of the host machine

Related Topic