- [David] With Docker, you're running your applications
inside containers.
Those containers, those applications are going to have
to store data at some point.
It's always recommended to store data inside Docker volumes
and get that data outside of containers,
as those provide better performance and isolation.
However, if you have a work load that needs persistent data
in the writable layer of your container,
you should look at storage drivers.
This is true no matter what version
of Docker you're running, no matter what edition,
Community or Enterprise,
and no matter what platform you're running Docker on.
Docker for Mac, Docker for Windows, it doesn't matter.
This stands true.
To find out what storage driver you're using,
you can use docker, space, info and we'll just pipe that
to more because the output is rather long.
You can see here, on this Docker for Mac installation,
our Storage Driver by default is overlay2,
but that Storage Driver can change based on the platform
that you have installed Docker on.
Docker has a plugable storage architecture
and it supports a number of different storage drivers.
The storage drivers control how images
and containers are stored on your Docker host.
If you'd like to learn more about storage drivers,
especially if you're preparing
for the Docker Certified Associate,
I recommend that you check out the,
Selecting a Storage Driver doc in the Docker documentation.
This talks about all the different storage drivers
that are available, including overlay2 which we just saw
as our default storage driver,
but all the other storage drivers including Btrfs, ZFS,
Device Mapper and others.
The instructions for changing
and configuring your storage driver
in Docker for Mac are all found here.