Normally relative paths are fine in vagrant files because vagrant up is run from the same directory as the Vagrantfile unfortunately the command vagrant global-status --prune may run the Vagrantfile from a different directory and then balk because it can't find dev/vagrant.local.yml
Normally relative paths are fine in vagrant files because
vagrant up
is run from the same directory as theVagrantfile
unfortunately the commandvagrant global-status --prune
may run theVagrantfile
from a different directory and then balk because it can't finddev/vagrant.local.yml