Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Docker Quickstart Terminal replaces coloms by semi-coloms #80
I'm trying to execute a container mapping the current directory on Windows, using the new "Docker Quickstart Terminal".
The problem is that the paths get changed before executing docker.
As you can see a valid path with the old boot2docker gets converted to a pseudo Windows style path replacing the : that separates the host and the container directories to a ;
Using a Windows style path doesn't help either
Same for me. This is really frustrating as I can't get any tutorial to work. I can't even use docker-compose as I'm using the container method for that, and it requires the -v switch too:
$ docker-compose up invalid value "C:\\Program Files\\Git\\var\\run\\docker.sock;C:\\Program Files\\Git\\var\\run\\docker.sock" for flag -v: bad mount mode specified : \Program Files\Git\var\run\docker.sock See 'C:\Program Files\Docker Toolbox\docker.exe run --help'.
@doxxx I've tried putting the extra slash at the start of the path on the right hand side of the colon but then I get "Bad Address" instead:
bash: /c/Program Files/Docker Toolbox/docker: Bad address
For anyone else having this problem I found a comment in another thread that helped clear it up. The double slash has to be at the beginning. Not after the colon.
Here is my working example now:
referenced this issue
Dec 9, 2015
the suggestion to put two slashes, "//c/", is not working for me. It creates the folder inside your docker container, but there is no persistence from my local C drive (files inside that folder are non-existent.
If you've gotten it to work using the double slashes, please give your full steps as my conclusion is either correct or misguided.
This looks to have been fixed for the docker binary when run from
however, there are issues when you're using something else - for example, #397
so - @jeffdm can we close this one?
Persisting only within the Windows "Users" directory is a bit too restrictive for some needs. Here is a work around that I use on a daily basis now:
first, ensure (using the GUI) that virtualbox has a shared folder setup to your liking (in this case we will map to a
get to your root directory in the linux machine
create a directory to share (persist) data with your local machine
mount the shared folder named "work" to the "/work" dir inside the Boot2Docker VM
run the container with the mounted "/work" volume located at "/work" inside the container