{"id":23587,"date":"2022-10-03T14:10:14","date_gmt":"2022-10-03T14:10:14","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=23587"},"modified":"2025-07-12T05:40:18","modified_gmt":"2025-07-12T05:40:18","slug":"creating-a-simple-parent-base-docker-image-using-scratch","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/creating-a-simple-parent-base-docker-image-using-scratch\/","title":{"rendered":"Docker Tutorials: Image – Creating a docker image using scratch"},"content":{"rendered":"\n

You can use Docker\u2019s reserved, minimal image, scratch, as a starting point for building containers. Using the scratch \u201cimage\u201d signals to the build process that you want the next command in the Dockerfile to be the first filesystem layer in your image.<\/p>\n\n\n\n

There is a scratch image on docker hub, but it’s essentially just the canvas for creating base images, it’s essentially useless until you setup an OS and create a new image from it. you’ll likely never need to use it unless you’ve written your own operating system, as just about every existing platform is already present in some form or another as a base image for you to build upon.<\/p>\n\n\n\n

The scratch image is the most minimal image in Docker<\/strong>. This is the base ancestor for all other images. The scratch image is actually empty. It doesn’t contain any folders\/files …<\/p>\n\n\n\n

The scratch image is mostly used for building other base images. For instance, the debian<\/a> image is built from scratch as such:<\/p>\n\n\n\n

FROM scratch  \nADD rootfs.tar.xz \/  \nCMD [\"bash\"]<\/pre>\n\n\n\n
The rootfs.tar.xz<\/a> contains all the files system files. The Debian image adds the filesystem folders to the scratch image, which is empty.<\/p>\n\n\n\n
While scratch appears in Docker\u2019s repository on the hub, you can\u2019t pull it, run it, or tag any image with the name scratch. Instead, you can refer to it in your Dockerfile. For example, to create a minimal container using scratch:<\/p>\n\n\n\n
FROM scratch
ADD hello \/
CMD [\"\/hello\"]<\/pre>\n\n\n\n
Assuming you built the \u201chello\u201d executable example from the Docker GitHub example C-source code<\/a>, and you compiled it with the -static flag, you can then build this Docker image using: docker build –tag hello .<\/p>\n\n\n\n
The scratch image is blank.The hello-world executable added to the scratch image is actually statically compiled, meaning that it is self-contained and doesn’t need any additional libraries to execute.<\/strong><\/p>\n\n\n\n
$ docker run --rm -it -v $PWD:\/build ubuntu:16.04\ncontainer# apt-get update && apt-get install build-essential\ncontainer# cd \/build\ncontainer# gcc -o hello -static -nostartfiles hello.c<\/pre>\n\n\n\n
Then you can run it (on Linux, Mac, or Windows) using: docker run –rm hello<\/p>\n\n\n\n
There are more example scripts for creating parent images in the Docker GitHub Repo:<\/p>\n\n\n\n