Skip to content
vagrant to configure VM environment
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Development installation


  1. Vagrant - tool for automation of virtual machine deployment.
  2. For MS Windows - Download and install vagrant from (tested on/recommended version vagrant 1.9.6)
  3. For Linux - use prefered package management
    1. Ubuntu:apt install vagrant
    2. Centos(RHEL):yum install vagrant
  4. Virtualbox - VM stack.
  5. For MS Windows - Download and install virtualbox (tested on/recommended version Virtualbox 5.1.22)
  6. For Linux - use preferred package management.
    1. Ubuntu: apt install virtualbox
    2. Centos(RHEL): yum install virtualbox

Brief instruction using Vagrant

The Vagrant tool configures and bootstraps virtual machine in Virtualbox. Brief instructions are:

git clone

cd wp6-vm

vagrant up

After succesfull installation, there should be message 'BOOSTRAP FINISHED, VM prepared to use'.

After 'vagrant up' has finished, the new virtual machine can be accessed via web browser (port 8080 is by default forwarded to VM, check VagrantFile or vagrant log for exact port number)


You can access the desktop of the VM by going into VirtualBox.

Detailed instruction

Download or clone metarepository ZIP (4kB) unzip it into some [wp6-vm directory] or clone the main repository

1. Open command-line (e.g. cmd, cygwin or terminal) and cd to directory where wp6-vm is unzipped/cloned

cd [wp6-vm directory]/[selected configuration]

These configurations are available:

  • Standalone from Source Codes (default) - based on CernVM 4.0 micro image which boots into Scientific Linux 7. Initial VM image size = 18MB, during boot and bootstrap downloads 658 MB. This is preferred option as CernVM distrtomaibutes most updated SL7 with recent security updates, so either restart or cernvm-update -a is required occasionally.
cd wp6-vm/vf-standalone-src/
cd wp6-vm
  • Standalone from Binaries (distributed via cvmfs). The same as above - but Virtual Folder is not compiled from sources -boots from cvmfs as well. This option is faster, the last stable release is distributed.
cd wp6-vm/vf-standalone-bin/
  • Standalone from Source Codes - based on clean Scientific Linux 7 - no dependency on online repositories at all. Initial VM image size = 665 MB, boot and bootstrap download 320 MB. Recommended for preparing off-line deployment.
cd wp6-vm/vf-standalone-src-sl7/
  • Test configurations - currently in testing stage, not guaranted to be working.
cd wp6-vm/test-...

2. (Optionally), if you have used west-life VM before, you may remove previous VM by and update the vagrant box cache

vagrant destroy
vagrant box update    

3. (Optionally), the master branch from sources are cloned, to change it, edit the file and uncomment/edit the following three lines (change 'dev' with a desired git branch):

# optional switch to branch
cd west-life-wp6
git checkout dev
cd ..

4. (Optionally), by default, virtualfolder in VM will contain single user environment. To enable multiuser environment with VRE, edit file and uncomment the following line. Default user for VF will then be vagrant/vagrant:


5. Start the vagrant box:

vagrant up    

This will start VM template, boots to Scientific Linux 7 and performs some bootstrap scripts. Depending on network speed it will take several to several tens of minutes - CernVM image (18MB) will need to download additional 200 MB, SL7 image (700 MB) will need to download additional 100 MB. Wait until "BOOTSTRAP FINISHED", otherwise the process failed, investigate the logs.


After 'vagrant up' finished, the new virtual machine can be accessed via web browser (port 8080 is by default forwarded to VM, check VagrantFile or vagrant log for exact port number)


Default login name to VRE is vagrant/vagrant.

Files of the current working directory of host are mounted into the guest /vagrant.

You can access the guest by SSH (default port 2222 is forwarded to VM)

vagrant ssh

or access GUI in virtualbox (username/password: vagrant/vagrant).

Uninstallation - Cleaning

6. After testing you may, stop (halt) the VM:

vagrant halt

7. If you will not use the VM anymore, you can delete (destroy) the VM:

vagrant destroy

Release Notes

  • 27/06/2017 - added variation of Vagrant scripts for different deployment type
  • 03/05/2017 - works with Vagrant version 1.9.3 and bellow or 1.9.5 and above. Vagrant version 1.9.3 needs to use different Vagrantfile, Vagrant version 1.9.4 has bug preventing to bootstrap the VM.
  • 25/11/2016 - Updated vagrant boxes to use uCernVM 2.7.7 bootloader, updated OVA images in and vagrant boxes, do "vagrant box update", bug fixes, consolidated initial web page and design, fixed/added background services
  • 26/10/2016 - moved VagrantFile to new repository, updated base box with uCernVM2.7.4 bootloader for CernVM 4 fixes security bug 'dirty COW' and aufs bug in kernel,,
  • tested on Windows 7 64 bit, vagrant 1.8.6 + VirtualBox 5.1.6, vagrant 1.8.1, 1.8.4, VirtualBox 5.0.26, note vagrant < 1.8.6 requires VirtualBox 5.0.x, doesn't require VirtualBox extension pack, download from
  • tested on Ubuntu 14.04 LTS, (default vagrant 1.4.3 needs to be updated to 1.8.6), default VirtualBox 4.3.36 works
You can’t perform that action at this time.