Phase 3Intermediate4 of 11 in Docker

Data & Volumes

Containers are disposable; your data usually isn't. This phase is about keeping the two separate on purpose.

Topic 1.1 showed that a container's writable layer disappears when the container is removed. For a stateless web server, that's fine. For a database, that's a catastrophe. Volumes are how Docker solves this.

0/3 · 0%

3 topics ~41 min 4 code blocks & diagrams

Start with the first topic

3.1

Why Containers Need Volumes

Delete a database container without a volume, and every row you ever inserted is gone forever. Volumes exist to make data outlive the container that produced it.

14 min 1 diagram 1 code practice

3.2

Named Volumes

The recommended, Docker-managed way to persist data — Docker decides where it physically lives, and you refer to it by a simple name.

14 min 1 code practice

3.3

Bind Mounts

Instead of letting Docker manage where data lives, you point directly at a specific folder on your own machine — the go-to tool for live-editing code during local development.

13 min 1 code practice

Command Palette

Why Containers Need Volumes

Named Volumes

Bind Mounts