A container runs one application process, while a Pod is the Kubernetes unit that wraps one or more containers with shared networking and storage.
A container is an isolated process, created from a container image, with its own filesystem and resource limits. Outside Kubernetes it also gets its own network stack. Kubernetes never schedules a container on its own, though. It schedules Pods, the smallest deployable unit.
Inside a Pod, the containers share one IP address and port space and can mount the same volumes. That lets a sidecar, a helper such as a log shipper or proxy, run next to the main container and reach it over localhost.
The usual Pod holds one container. Extra containers join it only when they must run and scale together.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓