Vagrant, VirtualBox, and Docker on woof

Latest news.

  • As of 2018-03-31, Vagrant was updated to 2.0.3 (from 1.8.5) and VirtualBox to 5.2.8_121009 (from 5.1). You will need to destroy and rebuild your vagrant boxes (and possibly destroy `$VAGRANT_HOME`).
  • As of 2018-03-22, Docker was updated automatically to 18.0.3 (from 17.12.1).

Getting started with Vagrant.

  • First, you should set your VAGRANT_HOME environment variable to a scratch area to avoid putting easily-reconstructible data in your backed-up home area. Example for .bashrc:
    # Configure vagrant directory outside backed-up space.
    if [[ -d "/scratch/$USER" ]]; then
     export VAGRANT_HOME="/scratch/$USER/.vagrant.d" 
    elif [[ -d "$HOME/scratch" ]]; then
     export VAGRANT_HOME="$HOME/scratch/.vagrant.d" 
  • Getting started with Vagrant
  • Creating an Ubuntu VM at FNAL

Getting started with Docker.

Updating Vagrant, VirtualBox and Docker.

  • New vagrant RPMs should be downloaded and installed from
  • Generally speaking, VirtualBox will update automatically via yum within a minor version. More significant updates must be done manually with yum list VirtualBox-\* and yum upgrade VirtualBox-<minor-ver>. If there are active boxes, the automatic update may fail. The following prescription should shut down all active boxes:
    for id in $(vagrant global-status --machine-readable | cut -d, -f5 | grep -B3 running | egrep -o "[0-9a-f]{7}"); do
        vagrant suspend $id;
  • Docker should update automatically via yum. If there are active containers, the process might be delayed.