Why does Docker recommend volumes over writing heavily into a container's writable layer for persistent application data?

Question

Accepted Answer

B. Volumes are Docker's preferred persistent storage mechanism and avoid growing the container writable layer. Docker documents volumes as the preferred mechanism for persistent data because they persist independently of the container lifecycle and do not bloat the container writable layer. They are also easier to back up or migrate than relying on writable-layer state. Docker does not claim that local volumes automatically solve encryption or cross-node sharing in every case.

Why does Docker recommend volumes over writing heavily into a container's writable layer for persistent application data?

Related Questions

Discussion