title: docker-machine and vagrant (in regards of mount volumes)
body: <p>Say I have a virtual box virtual machine provisioned through Vagrant. I then provision it with docker-machine - so far all good: I can <code>docker-machine ssh</code> into the box and list it ok with <code>docker-machine ls</code>.</p>
  
  <p>In the past, when not yet using dokcer-machine, my usual workflow would involve sshing into the virtual box, installing docker and spinning up my containers.</p>
  
  <p>As far as I understand this is not longer needed as I can control docker containers within the virtual box through docker-machine (and docker itself) from outside the virtual box (essentially from my win dev machine).</p>
  
  <p>Question: how can I mount directories from inside the vm into the container when I am running the docker command from outside the container?</p>
  
  <p>Example to further clarify:</p>
  
  <p>1) old approach. ssh into vbox and run</p>
  
  <pre><code>docker run -i -t --net=try-net \
  --name XXXX \
  -v ${PWD}/xxxx/yyyy.py:/zzzzz/xxxx/yyyy.py \
  -d me/image
  </code></pre>
  
  <p>2) docker-machine approach. I switch the docker-machine env onto the box. Now how do I reference a folder in the vbox from outside the box? Is this even possible?</p>
  
  <p>From my win host in a Linux like shell:</p>
  
  <pre><code>docker run -v /c/x/y/z:/home --name postgres3 -d postgres:9.5
  </code></pre>
  
  <p>gets me:</p>
  
  <p>c:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: Invalid bind mount spec "c:\x\y\z\;C:\Program Files (x86)\Git\home": invalid mode: \Program Files (x86)\Git\home.</p>