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

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

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

~ Answered on 2015-04-09 09:54:42