title: Using absolute path with docker run command not working
body: <p>What's the difference between these two docker run commands and why one is working and the other does not.</p>
  <p><strong>Working Command</strong></p>
  <p><code>docker run --publish=7474:7474 --volume=$HOME/neo4j_test/data:/data neo4j</code></p>
  <p><strong>Not Working</strong></p>
  <p><code>docker run --publish=7474:7474 --volume=C:/Users/USERNAME/neo4j_test/data:/data neoj</code></p>
  <p><code>docker run --publish=7474:7474 --volume=C:\Users\USERNAME\neo4j_test\data:/data neo4j</code></p>
  <p>Error for these commands</p>
  <blockquote>
  <p>C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: Invalid bind mount spec &quot;C:UsersUSERNAMEneo4j_testdata:/data&quot;: invalid mode: /data.
  See 'C:\Program Files\Docker Toolbox\docker.exe run --help'.</p>
  </blockquote>
  <p>In the non-working commands, I just replaced <code>$HOME</code> with the absolute path for my user profile folder <code>C:/Users/USERNAME</code></p>
  <p><strong>UPDATE</strong></p>
  <p>I did inspect the value for <code>$HOME</code> by executing <code>echo $HOME</code> on Windows Powershell. And it is in fact <code>C:\Users\USERNAME</code>. I also did look at the <a href="https://stackoverflow.com/questions/33312662/docker-toolbox-mount-file-on-windows">link</a> that @Titouan Freville has commented. So I used the command</p>
  <p><code>docker run --publish=7474:7474 --volume=/c/Users/USERNAME/neo4j_test/data:/data neo4j</code></p>
  <p>isntead of</p>
  <p><code>docker run --publish=7474:7474 --volume=C:/Users/USERNAME/neo4j_test/data:/data neoj</code></p>
  <p>and it is working now. Right now I'm just wondering where the transformation of <code>$HOME</code> from <code>C:\Users\USERNAME</code> to <code>/c/Users/USERNAME</code> happens</p>