Notes

5. Docker Multi-Stage Builds & Image Optimization

3 min read

🐳 Day 5: Docker Multi-Stage Builds & Image Optimization

Video Overview

This note explains the concept of Docker Multi-Stage Builds, how they help optimize image sizes, and why separating build and runtime environments is critical for production-ready containers.

📌 Core focus:

  • Build vs Runtime separation
  • Image size optimization
  • Practical Dockerfile implementation

🍕 Concept 1: Build vs Runtime (Pizza Analogy)

Quote

Anything required to build the application should NOT be part of the final image.

Think of making a pizza:

  • Build stage → Ingredients, tools (microwave, measuring cup)
  • Runtime stage → Eating the pizza 🍕

🧠 Key Idea

  • Build tools ≠ Runtime requirements
  • Final image should only contain what is needed to run the app

📉 Concept 2: Why Smaller Images Matter

Important

Smaller Docker images are faster, safer, and more efficient.

🚀 Benefits:

  • ⚡ Faster pull & push
  • 🚀 Faster deployment
  • 🔒 Reduced attack surface (more secure)
  • 💾 Less storage usage

⚙️ Concept 3: Compiled vs Interpreted Languages

Why this matters?

Determines whether your app needs a build stage

🧱 Compiled Languages

  • Require conversion to machine code
  • Need build tools (compilers)
  • Examples:
    • Java
    • C / C++
    • Go

🧾 Interpreted Languages

  • Run line-by-line via interpreter
  • No compilation required
  • Examples:
    • Python
    • JavaScript
    • PHP

🧠 Takeaway

  • Compiled → Heavy build stage required
  • Interpreted → Usually no build stage (but can still use multi-stage)

🐍 Concept 4: Example Application (Python Flask)

Application Details

  • Framework: Flask
  • Port: 5000
  • Output: Hello Docker

📄 Single Stage Dockerfile

FROM python:3.9
 
WORKDIR /app
 
COPY app.py /app
 
RUN pip install flask
 
EXPOSE 5000
 
ENTRYPOINT ["python"]
CMD ["app.py"]

🔧 Improvements in Dockerfile

Tip

Follow best practices for cleaner Dockerfiles

  • Use COPY instead of ADD
  • Use ENTRYPOINT + CMD together

⚠️ Problem: Unnecessary Build Tools

apt update
apt install -y build-essential

Warning

Build tools increase image size unnecessarily

📦 Result

  • Image size: ~495 MB

🏗️ Concept 5: Multi-Stage Dockerfile

Multi-Stage Build 

# Stage 1: Build Stage
FROM python:3.9 AS build
 
WORKDIR /app
COPY app.py .
 
RUN apt update && apt install -y build-essential
RUN pip install flask
 
# Stage 2: Final Runtime Stage
FROM python:3.9
 
WORKDIR /app
 
COPY --from=build /app .
 
RUN pip install flask
 
EXPOSE 5000
 
ENTRYPOINT ["python"]
CMD ["app.py"]

🔑 Key Instruction

COPY --from=build /app .

Important

Copies only required files from build stage → excludes heavy tools

📊 Concept 6: Size Comparison

Optimization Result

Image TypeSize
Single Stage495 MB
Multi-Stage162 MB

💥 Result

  • ~67% size reduction
  • Same functionality ✅

🧪 Running Containers

docker run -p 8080:5000 python-image
docker run -p 8081:5000 python-image-multi

🌐 Output

  • localhost:8080 → Hello Docker
  • localhost:8081 → Hello Docker

🧠 Final Takeaways

Summary

  • Multi-stage builds separate build & runtime
  • Remove unnecessary dependencies
  • Reduce image size drastically
  • Improve security & performance

📌 One-Line Summary

Quote

Build heavy → Ship light 🚀

Graph View