Interview Kubernetes, Docker, Helm & Podman

What is a .dockerignore file, and why does it matter?

Kubernetes, Docker, Helm & Podman · Advanced level

Answer

.dockerignore controls which files are excluded from the build context. It matters because sending secrets, git history, node_modules, test outputs, or large artifacts to the builder slows builds and can accidentally bake sensitive files into images.

Technical explanation

The build context is sent before Dockerfile instructions run, so .dockerignore improves performance even if files are never copied.

It also prevents accidental leakage of .env files, credentials, SSH keys, and local build artifacts.

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: add .dockerignore and measure build context size reduction.

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