In the previous lecture, we discussed about storage drivers.
Storage drivers help manage storage on images and containers.
We also briefly touched upon volumes in the previous lecture.
We learned that,
if you want to persist storage, you must create volumes.
Remember
that volumes are not handled by storage drivers.
Volumes are handled by volume driver plugins.
The default volume driver plugin is local.
The local volume plugin helps create a volume on the Docker host
and store its data
under the /var/lib/docker/volumes/ directory.
There are many other volume driver plugins
that allow you to create a volume on third-party solutions
Like Azure file storage, Convoy, DigitalOcean Block Storage,
Flocker, Google Compute persistent disks,
GlusterFS, NetApp, RexRay, Portworx, and VMware vSphere Storage.
These are just a few of the many.
Some of these volume drivers support different storage providers.
For instance,
RexRay Storage Driver can be used to provision storage
on AWS EBS,
S3,
EMC storage arrays like Isilon and ScaleIO,
or Google persistent disk
or OpenStack Cinder.
When you run a Docker container,
you can choose to use a specific volume driver,
such as the RexRay EBS
to provision a volume from Amazon EBS.
This will create a container
and attach a volume from the AWS Cloud.
When the container exits,
your data is safe in the cloud.
In the upcoming lectures,
we will see more about volumes in Kubernetes.