Interview Kubernetes, Docker, Helm & Podman

How do you reduce the size of a Docker image?

Kubernetes, Docker, Helm & Podman · Advanced level

Answer

I reduce image size with multi-stage builds, slim or distroless bases, .dockerignore, dependency pruning, cache cleanup in the same layer, and by avoiding unnecessary build tools or copied artifacts in the runtime image.

Technical explanation

Remove package manager caches in the same RUN layer where packages are installed.

Measure with docker history, dive, or build tool output rather than guessing where size comes from.

Container image quality affects supply chain, startup time, vulnerability surface, rollout reliability, and debugging workflows.

Prefer reproducible builds: pinned dependencies, small build context, deterministic Dockerfile order, non-root runtime, and immutable image references.

Understand the runtime boundary: an image is not a VM, and container isolation depends on kernel, namespaces, cgroups, capabilities, seccomp, and mounts.

Hands-on example

1. Create a tiny sample app and Dockerfile for this exercise: reduce image size and verify before/after with docker images and history.

2. Build and inspect it with docker build or podman build, docker history, image inspect, and a vulnerability or size scan if available.

3. Run it locally with explicit env vars, ports, user, volumes, and signal tests depending on the question.

4. Convert the final runtime assumptions into Kubernetes fields such as image, command, args, ports, securityContext, probes, and volumeMounts.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions