Interview Kubernetes, Docker, Helm & Podman

What is the difference between an image and a container?

Kubernetes, Docker, Helm & Podman · Intermediate level

Answer

An image is the packaged artifact, and a container is a running or stopped instance created from that image. Multiple containers can run from the same image with different config, environment, mounts, and network settings.

Technical explanation

Deleting a container does not delete the image unless explicitly removed.

Container runtime settings such as env, mounts, command, and ports are applied when the container is created.

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: create multiple containers from the same image with different commands/env.

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