## Notes Docker containers are meant to be stateless, so that containers can restart with very little downtime. However some cases require a container to be able to read data. Options - *volume* - *bind mount* ## Choosing the Right Type of Mount - Volumes are stored in a part of the host filesystem which is managed by Docker. Non-Docker processes should not modify this part of the filesystem. Volumes are the best way to persist data in Docker - Bind mounts may be stored anywhere on the host system. They may even be important system files or directories. Non-Docker processes on the Docker host or a Docker container can modify them at any time - `tmpfs` mounts are stored in the host system's memory only, and are never written to the host systems' filesystem ## Use Cases for Volumes - Sharing data among multiple running containers. A volume is create the first time it is mounted into a container. ## References - [Storage - Docker Docs](https://docs.docker.com/storage)