In the previous lesson, we discussed storage drivers, which manage storage for images and containers. We also briefly introduced volumes. Remember, if you want to persist data, you must create a volume. It is important to note that volumes are not managed by storage drivers; instead, they are handled by volume driver plugins. The default volume driver plugin in Docker is “local.” This plugin creates a volume on the Docker host and stores its data under theDocumentation Index
Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
Use this file to discover all available pages before exploring further.
/var/lib/docker/volumes directory. In addition to the local plugin, many other volume driver plugins enable you to create volumes on third-party storage solutions such as Azure File Storage, Convoy, DigitalOcean Block Storage, Flocker, Google Compute Persistent Disks, Cluster FS, NetApp, Rex Ray, Portworx, and VMware vSphere Storage, among others.
Some volume drivers support multiple storage providers. For instance, the Rex Ray storage driver supports the provisioning of storage on several platforms such as:
- AWS Elastic Block Store (EBS)
- Amazon S3
- EMC storage arrays like Isilon and ScaleIO
- Google Persistent Disk
- OpenStack Cinder

Use volume driver plugins to connect your containers to various cloud storage solutions, enabling scalable and persistent data storage across different environments.