Linux Docker Version 1.11.2 : Bug : Option --workdir breaks "docker run" inside Ubuntu/Trusty running in VirtualBox on Windows 8.1 #25052
Labels
area/runtime
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
version/1.11
Summary:
Inside a Ubuntu/Trusty VM (running in VirtualBox on Windows) the Docker run command with Option "
--workdir
" failes with Message "docker: Error response from daemon: Container command 'env' not found or does not exist..
" - even no other "Container command" got found ...BUG REPORT INFORMATION
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Output of
cat /etc/apt/sources.list.d/docker.list
:Output of
dpkg-query -l docker-engine
:Output of
uname -a
:Output of
lsb_release -da
:Steps to reproduce the issue:
using the command
sudo docker build --build-arg=https_proxy="http://www-cache.inf.h-brs.de:8080" --build-arg=http_proxy="http://www-cache.inf.h-brs.de:8080" --no-cache -t safe-docker docker-image
docker run [...many Options ...]
direct from linux bash like this:The result I received:
From abov
docker run
command I received this Error message:docker: Error response from daemon: Container command 'env' not found or does not exist..
The results I expected:
I expected the same result from abov
docker run
command, if I omit the option--workdir
like hereFrom that I received:
Additional information you deem important (e.g. issue happens only occasionally):
putting it into the workdir but
docker run ...
cannot find this program:docker: Error response from daemon: Container command 'mypath' not found or does not exist..
--workdir
also breaks docker run if it doesn't point to a per--volume
mounted path.--workdir
also breaks docker run if docker is running in a not virtualised TrusyBest regards,
Robert
The text was updated successfully, but these errors were encountered: