Error Cannot Start Container stat bin sh no such file or directory

Question

I have been trying to create my own busybox base image       mkimage sh -t pensu busybox busybox-static   mkdir -p  var tmp docker-mkimage US3tHy0uBQ rootfs   tar --numeric-owner -caf  var tmp docker-mkimage US3tHy0uBQ rootfs tar xz -C  var tmp docker-mkimage US3tHy0uBQ rootfs  --transform s            cat  gt    var tmp docker-mkimage US3tHy0uBQ Dockerfile    rm -rf  var tmp docker-mkimage US3tHy0uBQ rootfs   docker build -t pensu busybox  var tmp docker-mkimage US3tHy0uBQ Sending build context to Docker daemon 863 2 kB Sending build context to Docker daemon  Step 0   FROM scratch  --- gt   Step 1   ADD rootfs tar xz    --- gt  8eac78bfc9d6 Removing intermediate container ad9bbb8f7536 Successfully built 8eac78bfc9d6   rm -rf  var tmp docker-mkimage US3tHy0uBQ   I can see the image is available with my docker repo     docker images REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE pensu busybox       latest              8eac78bfc9d6        7 seconds ago       2 476 MB   But when I try to do docker run  I always get the error     docker run -it pensu busybox  bin sh exec    bin sh   stat  bin sh  no such file or directorytime  2015-04-09T16 03 45 05 30  level  fatal  msg  Error response from daemon  Cannot start container 8fe73b7832193c847d7975175a4be86d1f0b550b6a00b812bd4cdd18fe752468  exec     bin sh    stat  bin sh  no such file or directory     I am not able to understand why is it giving that error  Am I doing something wrong  How else can I validate that I am creating a correct image that is in working condition

User · Answer

On Windows  msys  using Docker Toolbox Machine  I had to add an extra   before  bin bash to indicate that it was a  nix filepath   So  docker run --rm -it  lt image gt  latest   bin bash

User · Answer

I had a similar problem   docker  Error response from daemon  OCI runtime create failed  container linux go 346  starting container process caused  exec    sh    executable file not found in  PATH   unknown    In my case  I know the image works in other places  then was a corrupted local image  I solved the issue removing the image  docker rmi  lt imagename gt   and pulling it again docker pull  lt imagename gt     I did a docker system prune too  but I think it s not mandatory

User · Answer

Explicitly mention the ubuntu version in the docker file which you are trying to RUN   FROM ubuntu 14 04   Dont use like FROM ubuntu Latest  This resolved my above  Cannot Start Container  stat  bin sh  no such file or directory  issue

User · Answer

This error      docker  Error response from daemon  OCI runtime create failed    container linux go 348  starting container process caused  exec       bin sh    stat  bin sh  no such file or directory   unknown    occurs when creating a docker image from base image eg  scratch  This is because the resulting image does not have a shell to execute the image  If your use   ENV EXECUTABLE hello cmd   EXECUTABLE    in your docker file  docker uses  bin sh to parse the input string  and hence the error  Inspecting on the image  your will find    docker inspect  lt image-name gt   Entrypoint                       bin sh                    -c                      HM APP                   This means that the ENTRYPOINT or CMD arguments will be parsed using  bin sh -c  The solution that worked for me is to parse the command as a JSON array of string e g   cmd   hello     and inspecting the image again     Entrypoint                      hello                  This removes the dependence on  bin sh the docker app can now execute the binary file  Example   FROM scratch    Environmental variables    Copy files ADD       Home dir WORKDIR  bin  EXPOSE 8083 ENTRYPOINT   hospitalms     Hope this helps someone in future

User · Answer

After you create image  check it with     docker inspect  image name    and check what you have in CMD option  For busy box it should be    Cmd            bin sh      Maybe you are overwritting CMD option in your   mkimage sh

User · Answer

check your image cmd using the command docker inspect image name   The output might be like this   quot Cmd quot          quot  bin bash quot        quot -c quot        quot   nop   quot        quot CMD    quot  bin bash  quot   quot      So use the command docker exec -it container id  bin bash  If your cmd output is different like this   quot Cmd quot          quot  bin sh quot        quot -c quot        quot   nop   quot        quot CMD    quot  bin sh  quot   quot      Use  bin sh instead of  bin bash in the command above

User · Answer

Using   docker inspect Incase the Image has no  bin bash in the output  you can use command below  it worked for me perfectly   docker exec -it  lt container id gt  sh

User · Answer

You have no shell at  bin sh  Have you tried docker run -it pensu busybox  usr bin sh

User · Answer

I hit this error   stat  bin bash  no such file or directory   when running the command   docker exec -it 80372bc2c41e  bin bash   The solution was to identify the kind of terminal  or shell  that is available on the container  To do so  I ran   docker inspect 80372bc2c41e   In the output from that command  I saw    Cmd           bin sh        -c        gunicorn -b 0 0 0 0 7082 server app app       This tells me that there s a  bin sh command available  and I was able to connect with   docker exec -it 80372bc2c41e  bin sh

[docker] Error: Cannot Start Container: stat /bin/sh: no such file or directory"

Examples related to docker

Examples related to busybox