Docker Volumes Explained: Stop Losing Data Every Time You Restart a Container

You spent two hours setting up your PostgreSQL container, seeded it with test data, ran your app against it — everything works perfectly. Then you restart the container. Gone. All of it. The database is empty again. If you have been there, you already know the pain. If you have not, consider this your warning. Docker containers are ephemeral by design, and that is a feature — until you forget about it and lose your data. This article is a practical guide to Docker volumes: what they are, how they work, when to use each type, and the patterns that will save you from the "where did my data go" panic at 2 AM. Why Containers Lose Data Every Docker container gets its own writable layer on top of its image. When you write files inside a running container, they go into this layer. The problem: when the container is removed (not just stopped, but removed), that writable layer is deleted with it. This is intentional. Containers are supposed to be disposable. You should be able to spin up ten co