Thursday, November 19, 2026

Image vs Container vs Pod: Three Words People Mix Up Every Day (Shared from LinkedIn)

Image vs Container vs Pod: Three Words People Mix Up Every Day

An attributed summary of a LinkedIn post by Turf Dev (published November 19, 2026). The box analogy and the framing are theirs; the notes below are my summary. See the original post for the full discussion.

The mix-up Turf Dev starts with is a common one: treating a Pod as just Kubernetes' word for a container. It isn't. An image, a container and a Pod are three different things, and confusing them is how files vanish after a restart and ports collide inside a Pod.

Image: the packed box

An image holds your app's files and settings, stacked in read-only layers. It never runs and never changes — shipping a new version means building a new image. One image can start a thousand containers, and it lives in a registry until a node pulls a copy.

Container: the box, running

A container is an ordinary process started from an image, running inside the isolation the earlier posts in this series covered. It gets one thin writable layer on top, and anything written there disappears when the container is replaced. If it crashes, the kubelet starts a fresh one from the same image, with an empty writable layer.

Pod: where they live together

A Pod is one or more containers that share a network — one IP, one set of ports, localhost between them. They can share volumes too, and they always run on the same node. Kubernetes schedules Pods, not containers. And a Pod is never repaired or moved: it is replaced, and the replacement gets a new IP.

Where the mix-up hurts

"My container restarted and my files are gone." They lived in the writable layer. Put them on a volume — an emptyDir survives container restarts.

"Two containers in my Pod both want port 8080." They share one network, so only one of them can have it.

"The IP survived a crash, then changed after a deploy." A crash restarts a container inside the same Pod, so the IP stays. A deploy creates new Pods, so the IP changes.

"We pinned the image by tag." Tags can move. A digest can't.

The one-line version

Image → what you ship. Container → what runs. Pod → what Kubernetes schedules.

This is post 05 in Turf Dev's "From chroot to Kubernetes CRI" series. Next up: Docker vs containerd vs CRI-O — who actually runs your containers?

Source: Turf Dev on LinkedIn, "Image vs container vs Pod: three words people mix up every day", November 19, 2026 — read the original post.

No comments: