WEBVTT

00:01.580 --> 00:05.100
In the previous lecture,
we discussed about storage drivers.

00:05.980 --> 00:10.190
Storage drivers help manage storage
on images and containers.

00:10.870 --> 00:14.240
We also briefly touched upon volumes
in the previous lecture.

00:14.560 --> 00:15.560
We learned that,

00:15.720 --> 00:19.440
if you want to persist storage,
you must create volumes.

00:19.630 --> 00:20.630
Remember

00:20.800 --> 00:23.980
that volumes are not handled
by storage drivers.

00:24.660 --> 00:27.590
Volumes are handled
by volume driver plugins.

00:28.420 --> 00:31.260
The default volume driver plugin
is local.

00:32.070 --> 00:35.980
The local volume plugin helps create
a volume on the Docker host

00:36.410 --> 00:37.650
and store its data

00:37.870 --> 00:40.890
under the /var/lib/docker/volumes/
directory.

00:42.980 --> 00:45.030
There are
many other volume driver plugins

00:45.200 --> 00:48.250
that allow you to create a volume
on third-party solutions

00:48.810 --> 00:53.320
Like Azure file storage, Convoy,
DigitalOcean Block Storage,

00:53.810 --> 00:56.600
Flocker,
Google Compute persistent disks,

00:57.100 --> 01:02.180
GlusterFS, NetApp, RexRay, Portworx,
and VMware vSphere Storage.

01:03.110 --> 01:04.860
These are just a few of the many.

01:06.020 --> 01:09.220
Some of these volume drivers
support different storage providers.

01:09.390 --> 01:10.390
For instance,

01:10.550 --> 01:13.320
RexRay Storage Driver
can be used to provision storage

01:13.490 --> 01:15.910
on AWS EBS,

01:16.370 --> 01:17.370
S3,

01:17.530 --> 01:20.370
EMC storage arrays
like Isilon and ScaleIO,

01:20.540 --> 01:21.960
or Google persistent disk

01:22.450 --> 01:23.630
or OpenStack Cinder.

01:25.060 --> 01:26.660
When you run a Docker container,

01:27.110 --> 01:30.370
you can choose
to use a specific volume driver,

01:30.560 --> 01:32.870
such as the RexRay EBS

01:33.350 --> 01:36.130
to provision a volume
from Amazon EBS.

01:37.420 --> 01:39.000
This will create a container

01:39.170 --> 01:42.050
and attach a volume
from the AWS Cloud.

01:42.860 --> 01:44.160
When the container exits,

01:44.620 --> 01:46.710
your data is safe in the cloud.

01:47.820 --> 01:49.070
In the upcoming lectures,

01:49.450 --> 01:52.590
we will see more about volumes
in Kubernetes.