Interview Kubernetes, Docker, Helm & Podman

What is a container image, and what are layers?

Kubernetes, Docker, Helm & Podman · Intermediate level

Answer

A container image is an immutable template made of layers plus metadata. Layers are content-addressed filesystem changes, which makes distribution and caching efficient because unchanged layers can be reused.

Technical explanation

Each Dockerfile instruction can create a layer, and layers are reused by digest when unchanged.

Image metadata includes config such as entrypoint, command, exposed ports, env vars, labels, and user.

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: build an image and inspect layers with docker history or podman 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