Skip to content
New issue

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

Linux Docker Version 1.11.2 : Bug : Option --workdir breaks "docker run" inside Ubuntu/Trusty running in VirtualBox on Windows 8.1 #25052

Open
ifrh opened this issue Jul 26, 2016 · 1 comment
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

Comments

@ifrh
Copy link

ifrh commented Jul 26, 2016

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:

praktomat@praktomat-tng-VirtualBox:~/inst4git$ docker version
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:47:50 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:47:50 2016
 OS/Arch:      linux/amd64
praktomat@praktomat-tng-VirtualBox:~/inst4git$ 

Output of docker info:

praktomat@praktomat-tng-VirtualBox:~/inst4git$ docker info
Containers: 7
 Running: 0
 Paused: 0
 Stopped: 7
Images: 29
Server Version: 1.11.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 42
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: host bridge null
Kernel Version: 3.13.0-79-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: praktomat-tng-VirtualBox
ID: RRRW:Z4DI:323W:4OUI:6K73:YDCW:OIP5:6N7S:GWNS:QMYY:W7XX:GOJQ
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Http Proxy: http://www-cache.inf.h-brs.de:8080
Https Proxy: http://www-cache.inf.h-brs.de:8080
Registry: https://index.docker.io/v1/

Additional environment details (AWS, VirtualBox, physical, etc.):

Output of cat /etc/apt/sources.list.d/docker.list:

cat /etc/apt/sources.list.d/docker.list 
deb https://apt.dockerproject.org/repo ubuntu-trusty main

Output of dpkg-query -l docker-engine:

Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name                              Version               Architektur           Beschreibung
+++-=================================-=====================-=====================-=======================================================================
ii  docker-engine                     1.11.2-0~trusty       amd64                 Docker: the open-source application container engine

Output of uname -a:

Linux praktomat-tng-VirtualBox 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Output of lsb_release -da:

lsb_release -da 
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:        14.04
Codename:       trusty

Steps to reproduce the issue:

  1. Install Ubuntu/Trusty (64bit) inside Virtualbox (Oracle VirtualBox 4.3.28 r100309) on Windows 8.1 (64bit)
  2. Install docker-engine inside Trusty (following docs: https://docs.docker.com/engine/installation/linux/ubuntulinux/ )
  3. Create the Docker image using dockerfile from https://github.com/KITPraktomatTeam/Praktomat/blob/master/docker-image/Dockerfile after commenting out their lines for Isabelle2016 support (line 62 to line 65)
    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
  4. Interact with the Docker via script from https://github.com/nomeata/safe-docker or calling docker run [...many Options ...] direct from linux bash like this:
docker run --rm --read-only --sig-proxy --tmpfs /tmp --tmpfs /run --tmpfs /home --net=none --memory=1G --user=1000:1000 --volume=/home/praktomat/inst4git/h_brs_p/Praktomat/src/checker/scripts:/home/praktomat/inst4git/h_brs_p/Praktomat/src/checker/scripts:ro --volume=/home/praktomat/inst4git/h_brs_p/debug-work/SolutionSandbox/tmpzF5jVE:/home/praktomat/inst4git/h_brs_p/debug-work/SolutionSandbox/tmpzF5jVE --workdir=/home/praktomat/inst4git/h_brs_p/debug-work/SolutionSandbox/tmpzF5jVE --name secure-tmp-b9f0f6ab-8d74-46bf-a814-e52feb6c8a34 safe-docker env

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 here

docker run --rm --read-only --sig-proxy --tmpfs /tmp --tmpfs /run --tmpfs /home --net=none --memory=1G --user=1000:1000 --volume=/home/praktomat/inst4git/h_brs_p/Praktomat/src/checker/scripts:/home/praktomat/inst4git/h_brs_p/Praktomat/src/checker/scripts:ro --volume=/home/praktomat/inst4git/h_brs_p/debug-work/SolutionSandbox/tmpzF5jVE:/home/praktomat/inst4git/h_brs_p/debug-work/SolutionSandbox/tmpzF5jVE  --name secure-tmp-b9f0f6ab-8d74-46bf-a814-e52feb6c8a34 safe-docker env

From that I received:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=79b1ac67f8e0
HOME=/

Additional information you deem important (e.g. issue happens only occasionally):

  • The issue happens for me every time.
  • Down grading docker-engine doesn't help.
  • I also wrote an own static compiled c program, which should print getenv(...)-Values,
    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..
  • I don't know if --workdir also breaks docker run if it doesn't point to a per --volume mounted path.
  • I don't know if --workdir also breaks docker run if docker is running in a not virtualised Trusy

Best regards,
Robert

@ifrh ifrh changed the title Option --workdir breaks "docker run" inside Ubuntu/Trusty running in VirtualBox on Windows 8.1 Linux Docker Version 1.11.2 : Bug : Option --workdir breaks "docker run" inside Ubuntu/Trusty running in VirtualBox on Windows 8.1 Jul 27, 2016
@thaJeztah thaJeztah added 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 labels Sep 12, 2016
@ifrh
Copy link
Author

ifrh commented Apr 10, 2021

any updates since then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants