The size of the Docker image could quickly increase during the build time. I became more mindful of the image size when I started to deploy on Github Actions. The bigger the image size, the longer the run time and the higher the runtime cost.
This is when you should consider using a multi-stage build 🚀.
(2/4) 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐚 𝐦𝐮𝐥𝐭𝐢-𝐬𝐭𝐚𝐠𝐞 𝐛𝐮𝐢𝐥𝐝?
Multi-stage is a build approach that includes the following two steps:
:l1: The first build - installing the required decencies and building the binaries. This image is also called the builder image
:l2: The second build - starting from a new base image and copying from the builder image binaries applications
(3/4) 𝐖𝐡𝐞𝐧 𝐬𝐡𝐨𝐮𝐥𝐝 𝐲𝐨𝐮 𝐮𝐬𝐞 𝐚 𝐦𝐮𝐥𝐭𝐢-𝐬𝐭𝐚𝐠𝐞 𝐛𝐮𝐢𝐥𝐝?
You should consider moving your build to a multi-stage build when the build-required dependencies are no longer needed after the build is completed. A classic example is when building a binary application. Also, this is effective when setting up a dockerized Python environment using a virtual environment.
Add comment