Throughout this chapter, we have reviewed how to manage data associated with containers. We took a look at different strategies to manage the data of processes and their statuses. We used host filesystems and unnamed and named volumes, and we learned how to extend the available Docker daemon volume management functionality by using plugins. We noticed that the Docker daemon will not take care of any application lock or even determine how storage resources are defined at the host level.
There are two different options for mounting volumes or bind mounts on containers using --volume or --mount. We also reviewed all the parameters required and the differences between them.
We talked about how to manage data and process states in high-availability environments. We haven't introduced any orchestration concepts yet, but it is important to understand that high availability or multiple instances of a process will require special application logic. Docker will not manage that logic...