# Image vs Container — Docker

Source: https://www.geekswithgeeks.com/en/docker/docker-image-vs-container

> An image is a blueprint; a container is a running instance of it.

## Two different things

An **image** is a read-only template — your app's filesystem, dependencies, and startup command frozen in layers. A **container** is a running (or stopped) instance created from an image, with its own writable layer.

## Class vs object

If you know OOP: an **image** is like a class, and a **container** is like an object created from it. You can spin up many containers from the same image.