how to use virtualbox for shell scripting

VAGRANT_DEFAULT_PROVIDER – By default Vagrant is using Virtualbox as its virtualization provider unless requested otherwise.

On or want to submit bug report with log for example. By default is ‘info’, change this to ‘debug’ in case you really want to know what’s going

VAGRANT_LOG – Verbosity level of Vagrant log messages.

It can get quiet large since it will contain all the base boxes.

VAGRANT_HOME – This is the directory where Vagrant stores its global state.

By default it’s ‘.vagrant’ in the same directory as your

VAGRANT_DOTFILE_PATH> – This is the directory where Vagrant stores VM-specific state.

However, I will point out number of important ones you should be familiar with: Vagrant environment variablesīy default Vagrant comes with sane default values and you don’t need to change any to make it work.

VirtualBox is a free multi-platform virtualization software which is supported by Vagrant out of the box. For this tutorial I’ll assume you have installed Oracle’s VirtualBox. Since Vagrant is not a virtualization software by itself, it relies on 3rd party providers for doing the virtualization part. In this tutorial I will use Vagrant 1.6.5. A lot of times the official repositories contains very old versions of Vagrant. I strongly suggest that you will install Vagrant from its website and not by using your package manager. Installation is simple “Next, Next, Next, Done” process and doesn’t require any special user interaction. Vagrant installation packages are available for OS X, Windows and Linux (deb and rpm format). In this tutorial I’ll show how can we take Vagrant as use it to create small virtual test lab which we will be able to pass to our colleagues. Speeding up the work with non multi-platform tools such as Docker.

While officially described as a tool for setting up development environments, Vagrant can be used for a lot of other purposes by non developers as well:

How to use virtualbox for shell scripting