title: Docker container doesn't see files on windows volumes when the volume endpoint isn't on the drive C:
body: <p>I want to use a docker image in my work process. For example I want to use larryprice/sass to compile my SASS files to CSS. This image is pretty simple:</p>
  
  <pre><code>FROM ruby:2.2 
  RUN gem install sass 
  WORKDIR /tmp 
  ENTRYPOINT ["sass", "--watch", "/src"]
  </code></pre>
  
  <p>I'm using Windows 10, Docker 1.11 and VirtualBox 5.0.16.</p>
  
  <p>My project files placed on work SSD, that mapped to logical drive D - 
  D:\Projects\Foo\Bar\web\sass</p>
  
  <p>So, my problem is following: when I attach a volume to the container from drive D: (by $PWD or by full path in MINGW style /D/Projects/Foo/Bar/web/sass) e.g.</p>
  
  <pre><code>cd /D/Projects/Foo/Bar/web
  docker run --name sass -v $PWD/sass:/src --rm larryprice/sass
  </code></pre>
  
  <p>the container can't see any SASS files:</p>
  
  <pre><code>$ docker exec -i -t sass /bin/bash
  root@541aabac9ceb:/tmp# ls -al /src/
  total 4
  drwxr-xr-x  2 root root   40 May  3 13:05 .
  drwxr-xr-x 50 root root 4096 May  3 13:05 ..
  </code></pre>
  
  <p>But when I mount a volume from system disk (C:) all works fine:</p>
  
  <pre><code>$ docker run --name sass -v ~/sass:/src --rm larryprice/sass
  [Listen warning]:
    Listen will be polling for changes. Learn more at https://github.com/guard/listen#polling-fallback.
  &gt;&gt;&gt; Sass is watching for changes. Press Ctrl-C to stop.
  &gt;&gt;&gt; New template detected: ../src/test.sass
        write /src/test.css
        write /src/test.css.map
  </code></pre>
  
  <p>How I can mount volumes from any place I need in Windows? Or what I'm doing wrong in my case?</p>
  
  <p>p.s. Add leading slash to the path also not working: </p>
  
  <pre><code>docker run --name sass -v //d/Projects/Foo/Bar/web/sass:/src --rm larryprice/sass
  </code></pre>