{"id":14076,"date":"2022-10-03T14:21:06","date_gmt":"2022-10-03T14:21:06","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=14076"},"modified":"2025-07-12T05:40:16","modified_gmt":"2025-07-12T05:40:16","slug":"how-to-optimize-faster-builds-and-smaller-docker-images-using-multistaging-build","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/how-to-optimize-faster-builds-and-smaller-docker-images-using-multistaging-build\/","title":{"rendered":"Docker Tutorials: Image – Optimize faster builds and smaller docker images using multistaging build?"},"content":{"rendered":"\n

Problem with traditional approach of creating docker image?<\/h2>\n\n\n\n

One of the most challenging things about building images is keeping the image size down. Each instruction in the Dockerfile adds a layer to the image, and you need to remember to clean up any artifacts you don\u2019t need before moving on to the next layer.<\/p>\n\n\n\n

It was actually very common to have one Dockerfile to use for development (which contained everything needed to build your application), and a slimmed-down one to use for production, which only contained your application and exactly what was needed to run it. This has been referred to as the \u201cbuilder pattern\u201d. Maintaining two Dockerfiles is not ideal.<\/p>\n\n\n\n

What is Docker multistaging build?<\/h2>\n\n\n\n

Multi-stage builds are a method of organizing a Dockerfile to minimize the size of the final container, improve run time performance, allow for better organization of Docker commands and files, and provide a standardized method of running build actions. A multi-stage build is done by creating different sections of a Dockerfile, each referencing a different base image. This allows a multi-stage build to fulfill a function previously filled by using multiple docker files, copying files between containers, or running different pipelines.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Before multi-stage builds<\/h2>\n\n\n\n