title: Vagrant provision using files included in .box from packer
body: <p>I'm building a vagrant .box file using packer.  I've got something like this in my packer .json config:</p>
  
  <pre><code>"post-processors": [
  //SNIP
    "include": [
      "./choco.ps1",
      "./vagrantUp.ps1",
      ]
  ]
  </code></pre>
  
  <p>It's building the .box, and if I manually untar the file I can see those are included in there.  When I end up running "vagrant box add Mybox <a href="http://whatever" rel="nofollow">http://whatever</a>" I can even see them in my ~/.vagrant.d/boxes/MyBox/0/virtualbox folder.</p>
  
  <pre><code> ~ $ ls ~/.vagrant.d/boxes/MyBox/0/virtualbox/
  Vagrantfile                 metadata.json
  box.ovf                     packer-virtualbox-iso-1424829938-disk1.vmdk
  choco.ps1                   vagrantUp.ps1
  </code></pre>
  
  <p>Also, in my packer vagrant template I have a line:</p>
  
  <pre><code>config.vm.provision  "shell", path: "vagrantUp.ps1"
  </code></pre>
  
  <p>Next, I want to initialize this machine.  I did the following:</p>
  
  <pre><code>~ $ cd ~/Vagrant
  Vagrant $ Vagrant mkdir MyBox; cd MyBox
  MyBox $ vagrant init MyBox
  MyBox $ ls
  VagrantFile
  </code></pre>
  
  <p>This file looks like the basic vagrant default, but at the top it mentions <code>config.vm.box = "MyBox"</code>.</p>
  
  <p>But then if I <code>vagrant up</code>, I get the following error:</p>
  
  <pre><code>* `path` for shell provisioner does not exist on the host system: /Users/me/Vagrant/MyBox/vagrantUp.ps1
  </code></pre>
  
  <p>It looks to me like the VagrantFile in /Vagrant/MyBox is referencing the VagrantFile in ~/.vagrant.d/, which is good, that's what I want.  But then it's still using the paths relative to /Vagrant/MyBox, when the files are actually relative to ~/.vagrant.d/</p>
  
  <p>Am I missing a step that tells vagrant to copy those files to the instance directory?  Or am I referencing them incorrectly in my vagrant template?</p>