Why Container filesystem is ephemeral in Docker? - Purpose & Use Cases

The Big Idea

What if all your work vanished every time you closed your app? Containers do that by default!

The Scenario

Imagine you run a software inside a container and make some changes to files while it's running. Then, you stop the container and start it again later. You expect your changes to still be there, but they are gone!

The Problem

Manually managing file changes inside containers is frustrating because containers don't save changes after they stop. This means you lose work, have to redo setups, and can't keep important data easily.

The Solution

Understanding that the container filesystem is ephemeral helps you plan better. You can use special storage areas called volumes to keep data safe outside the container's temporary space.

Before vs After

✗ Before

docker run myapp
# make file changes inside container
# stop container
# start container again
# changes lost

✓ After

docker run -v mydata:/app/data myapp
# changes saved in volume
# stop and start container
# changes persist

What It Enables

This concept lets you keep important data safe and share it between containers, making your apps reliable and easy to manage.

Real Life Example

A developer runs a database inside a container. Without volumes, all data disappears when the container stops. Using volumes, the database keeps all records safe even after restarts.

Key Takeaways

Containers erase file changes when stopped.

Data must be stored outside containers to persist.

Volumes solve the problem by saving data safely.