exec: "/bin/sh": stat /bin/sh: no such file or directory

[mitchellh]

exec: "/bin/sh": stat /bin/sh: no such file or directory

[gangster]

Seeing this too...

[dduportal]

Hi !

It seems related to the AUFS backend of Docker itself : moby/moby#5135.
There is a known limit of 127 layers when using this storage backend. I think that your custom ubuntu image have a lot of layers.

Solution 1 : flatten your build

It can be a quick-win solution in your case.
Reading @yangtao309 Dockerfile, i see some things to change :

• When using apt-get, put updates and install on the same line or you'll run in trouble (If apt-get update layer is cached with the version 1.0 of your package, the install will fail when 2.0 will be available as default). Anyway, you'll push the AUFS-127's limit

RUN apt-get update && apt-get install -y software-properties-common

• I see what you're doing with different sections (one for java, one for maven, etc.), but using Docker cache should be considered when developing you image. One time the image has been built, the loop of changes won't be often : you should group you action (apt-get install all packages in one layer, run all shell script action on only one RUN)

RUN apt-get update && apt-get install -y software-properties-common maven opens-server ...

• WORKDIR is a cool instruction when working with some wget/tar but it creates unused layers (it stole some precious layers when running around 127 and it weight a lot !). You should use it only one time at the end.

# install karaf
RUN cd /home/runner \
    && wget -q http://repo2.maven.org/maven2/org/apache/karaf/apache-karaf/2.3.4/apache-karaf-2.3.4.tar.gz \
    && tar xzvf apache-karaf-2.3.4.tar.gz \
    && mv apache-karaf-2.3.4 apache-karaf \
    && rm -f apache-karaf-2.3.4.tar.gz

A little bit of reading around that :

• http://www.centurylinklabs.com/optimizing-docker-images/?hvid=2b3AmY
• http://tuhrig.de/flatten-a-docker-container-or-image/

Solution 2 : switch Docker's storage backend

How to switch backend and use devicemapper instead of AUFS (or any other existing) ?
In boot2docker, you just have to :

• Set a var in a Shell file :
  In /var/lib/boot2docker/profile (create it if not existing), add this line

DOCKER_STORAGE=devicemapper

• Restart docker :

sudo /etc/init.d/docker restart

It will be persisted across reboots. Note you'll have to rebuild all (cache is not shareable between AUFS and others backends).

A little bit of (quick) reading around these storage backends : http://www.projectatomic.io/docs/filesystems/

Good luck !

[yangtao309]

@dduportal
solution 1 is ok!
thank you very much.
this issue i will be closed.