We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Without using --entrypoint, I check bash path.
$ winpty docker container run -ti ubuntu root@d8e47ed3fa6a:/# which bash /bin/bash root@d8e47ed3fa6a:/# exit exit
If I use explicit entry point I should get a bash session
$ winpty docker container run -ti --entrypoint /bin/bash ubuntu root@d8e47ed3fa6a:/#
Gets confused with --entrypoint parameter which seems to be mixed with a local path.
$ winpty docker container run -ti --entrypoint /bin/bash ubuntu root@d8e47ed3fa6a:/# C:/Program Files/Docker/Docker/resources/bin/docker.exe: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"C:/Program Files/Git/usr/bin/bash.exe\": stat C:/Program Files/Git/usr/bin/bash.exe: no such file or directory": unknown.
winpty docker container run -ti --entrypoint /bin/bash ubuntu
The text was updated successfully, but these errors were encountered:
This is due to Mingw/msys2 doing automatic path conversion; see http://www.mingw.org/wiki/Posix_path_conversion
You can disable this by prefixing paths with // or setting the MSYS_NO_PATHCONV=1 environment variable (see https://stackoverflow.com/a/34386471)
//
MSYS_NO_PATHCONV=1
Because this path conversion happens before docker receives the value, its not something we can fix in docker.
Hope this helps!
Sorry, something went wrong.
Closing as this is due to the shell, not docker.
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
No branches or pull requests
Expected behavior
Without using --entrypoint, I check bash path.
If I use explicit entry point I should get a bash session
Actual behavior
Gets confused with --entrypoint parameter which seems to be mixed with a local path.
Information
Steps to reproduce the behavior
winpty docker container run -ti --entrypoint /bin/bash ubuntu
The text was updated successfully, but these errors were encountered: