bug in Vagrant with Virtualbox sharefolder

  • August 23, 2015

The problem: serving static files

The problem will affect you if you try to serve static files from your vagrant folder if you use the default from virtualbox

For example you got your nginx or apache to serve css files and when you update them, they don’t get updated, and sometimes they even come out with some garbage bytes at the end of it

The reason, a long standing bug in virtual box

after reading this bug report in vagrant repository

I’ve found that the underlying bug is from virtualbox, bug which has been reported here

The solutions: deactivate send or switch of sharefolder type

If you use Nginx or apache you can just followed the official workaround

In Nginx:

sendfile off;

In Apache:

EnableSendfile Off

If you are like me and you’re serving your files from go then you have no other choice than to swithc the sharefolder type, nfs for Unix-ish OS and SMB for windows

A colleague of mine made this to have a transparent switch for your developers

def host_box_is_unixy?
  (RUBY_PLATFORM !~ /cygwin|mswin|mingw|bccwin|wince|emx/)

Vagrant.configure(2) do |config|

   # your stuffs

  if host_box_is_unixy?
    config.vm.synced_folder "./", "/vagrant", type: "nfs"
    config.vm.synced_folder "./", "/vagrant", type: "smb", mount_options: ['ip='] #host side of :private_network
    config.vm.network "private_network", ip: ""

NFS and SMB sharefolder don’t have this bug so you should be fine with that