How We Cut Our Docker Image Size by 80% and Why It Matters
A real walkthrough of shrinking bloated Docker images from 1.2GB to 240MB using multi-stage builds, Alpine, and dependency auditing.
On this page
Our main API image had grown to 1.2GB. Deploys were slow, registry costs were climbing, and cold starts on Kubernetes took 45 seconds. Here's exactly how we fixed it.
The Problem
A quick docker history revealed the culprits:
- Full Node.js 18 base image (900MB layer)
- Dev dependencies included in the final image
- Leftover build artifacts and cache directories
Step 1: Multi-Stage Builds
We split the Dockerfile into build and runtime stages:
# Build stage
FROM node:18 AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
# Runtime stage
FROM node:18-alpine AS runtime
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package*.json ./
EXPOSE 3000
CMD ["node", "dist/index.js"]
This alone dropped us from 1.2GB to 480MB.
Step 2: Prune Dev Dependencies
We added a production-only install in the runtime stage:
FROM node:18-alpine AS runtime
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY package*.json ./
RUN npm ci --omit=dev && npm cache clean --force
Down to 310MB.
Step 3: Audit What's Left
Running npx depcheck found 12 unused packages. We removed them and dropped another 70MB.
Results
| Metric | Before | After |
|---|---|---|
| Image size | 1.2GB | 240MB |
| Pull time | 38s | 8s |
| Cold start | 45s | 12s |
| Registry cost | $180/mo | $40/mo |
Best Practices
- Always use multi-stage builds for compiled or bundled applications
- Use Alpine or distroless base images in production
- Run
npm ci --omit=devto exclude dev dependencies - Add a .dockerignore to prevent copying node_modules, .git, and test files
- Audit images quarterly with
docker scoutortrivy
Small images mean faster deploys, cheaper storage, and a smaller attack surface. There's no reason to ship your test framework to production.
Cite this article
Kiril Urbonas (2026). How We Cut Our Docker Image Size by 80% and Why It Matters. DevOpsNess. https://www.devopsness.com/blog/how-we-cut-our-docker-image-size-by-80-and-why-it-matters
[How We Cut Our Docker Image Size by 80% and Why It Matters](https://www.devopsness.com/blog/how-we-cut-our-docker-image-size-by-80-and-why-it-matters) (Kiril Urbonas, DevOpsNess, 2026-03-28)
More from DevOps
Explore more articles in this category
GitHub Copilot CLI Sandboxing Is GA: What Actually Changed
GitHub made local sandboxing generally available for Copilot CLI on October 7. It is still off until you run /sandbox enable or your enterprise requires it.
Common Git Errors and How to Fix Them (2026 Guide)
Rejected pushes, local changes that would be overwritten, merge conflicts, detached HEAD, unrelated histories, publickey denials, and oversized files. What each message means and the safe fix.
PersistentVolumeClaim Stuck Pending: How to Fix It
A PVC stuck in Pending means nothing on the cluster can hand it a volume. Here's how we read the events and get it bound fast.
You might have missed
Evergreen posts worth revisiting.