Docker containers are great (my opinion) due to their ease of deployment and updating, as well as better resource usage for multiple concurrent services on a server. One could also argue they offer better security due to the potential ways you can isolate them from each other, and even your network (see an upcoming video of mine about this point).
A docker container on its own though does not retain any transactional data (persistence) if it is destroyed or updated. To achieve persistence, one creates volumes, which essentially map locations out to the OS side. Destroy or update the container, and it can still read that data from the volume.
This video explains quite clearly the 3 different ways to define such volumes.
Watch
Docker Volumes explained in 6 minutes
by TechWorld with Nana on YouTube#
technology #
docker #
container #
volume #
storage