moby: docker run ubuntu:14.04 /bin/echo 'Hello world' fails on new Wndows boot2docker install

initializing… Virtual machine boot2docker-vm already exists

starting… Waiting for VM and Docker daemon to start… …ooo Started. Writing C:\Users\lwilson.boot2docker\certs\boot2docker-vm\ca.pem Writing C:\Users\lwilson.boot2docker\certs\boot2docker-vm\cert.pem Writing C:\Users\lwilson.boot2docker\certs\boot2docker-vm\key.pem

To connect the Docker client to the Docker daemon, please set: export DOCKER_HOST=tcp://192.168.59.103:2376 export DOCKER_CERT_PATH=‘C:\Users\lwilson.boot2docker\certs\boot2docker-vm’ export DOCKER_TLS_VERIFY=1

IP address of docker VM: 192.168.59.103

setting environment variables … Writing C:\Users\lwilson.boot2docker\certs\boot2docker-vm\ca.pem Writing C:\Users\lwilson.boot2docker\certs\boot2docker-vm\cert.pem Writing C:\Users\lwilson.boot2docker\certs\boot2docker-vm\key.pem export DOCKER_HOST=tcp://192.168.59.103:2376 export DOCKER_CERT_PATH=‘C:\Users\lwilson.boot2docker\certs\boot2docker-vm’ export DOCKER_TLS_VERIFY=1

You can now use docker directly, or boot2docker ssh to log into the VM. Welcome to Git (version 1.9.5-preview20150319)

Run ‘git help git’ to display the help index. Run ‘git help <command>’ to display help for specific commands.

lwilson@LENOVO-LAPTOP ~ $ docker run ubuntu:14.04 /bin/echo ‘Hello world’ FATA[0000] Error response from daemon: Cannot start container 5ecfa25102f612cad0208ecc0a0a18507279bce72ef313ff5a9bc7cf786c11b: [8] System error: exec: “C:/Program Files (x86)/Git/bin/echo”: stat C:/Program Files (x86)/Git/bin/echo: no such file or directory

lwilson@LENOVO-LAPTOP ~

YES, the folder exists …

lwilson@LENOVO-LAPTOP ~ $ “C:/Program Files (x86)/Git/bin/echo” hi hi

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 18 (4 by maintainers)

Most upvoted comments

The rules: http://www.mingw.org/wiki/Posix_path_conversion

gmanfunky on Aug 8, 2015

This is due to msys-git trying to be smart and fixing up windows path and linux paths with all sorts of voodoo before passing them as process parameters.

Using a double forward-slash bypasses much of this voodoo.

It is a pretty aggravating problem to me too. I have to fixup various things to attempt docker development on windows.

For example, in bash on windows

$ docker run --privileged --rm -ti -v `pwd`:/go/src/github.com/docker/docker dry-run-test /bin/bash

Will fail.

$ docker run --privileged --rm -ti -v /`pwd`:/go/src/github.com/docker/docker dry-run-test //bin/bash

Will work.

I think I’ll make an issue for it. Some stuff has changed in this msys voodoo in the last year. I’m wondering if it messed us up, or if we just need to work around it.

gmanfunky on Aug 8, 2015

Double slash also worked for me - spent 5 hours trying to work it out . Thanks @iainsproat .

andy4545 on Jul 14, 2015