- Storage drivers — implement how a container’s writable layer and image layers are managed on the host filesystem (examples: overlay2, aufs, devicemapper). Storage drivers operate at the container runtime level and determine how container filesystem changes are isolated and persisted on the host.
- Volume driver plugins — provide integration with external or specialized storage backends (examples: NFS, cloud block storage, third-party plugins). Volume drivers enable containers to use persistent storage that outlives the container process and can be shared, mounted, or managed by external systems.

If you already know Docker’s storage drivers and volume plugins, you can skip this lesson. Otherwise, continue — understanding these concepts will make Kubernetes storage much clearer.
How storage drivers and volume plugins differ
- Storage drivers (runtime-level) manage the container image layers and the container’s writable layer. They determine copy-on-write behavior, layer merging, and how changed files are stored on the host.
- Volume plugins (external backends) expose persistent mounts to containers and let you attach storage that survives container restarts, can be shared between containers, or implemented by remote systems.
- Storage drivers: overlay2, aufs, devicemapper
- Volume plugins/backends: NFS, Amazon EBS, Google Persistent Disk, GlusterFS
Quick comparison
Inspecting Docker storage on a host
To see which storage driver Docker is using:- Run:
- Or to print only the storage driver:
Driver field programmatically.)
Why this matters for Kubernetes
Kubernetes separates concerns further:- Container runtimes still use storage drivers to manage image and writable layers on nodes.
- Kubernetes uses PersistentVolumes (PV) and PersistentVolumeClaims (PVC) to provide portable, declarative, and managed storage for workloads.
- The Container Storage Interface (CSI) standardizes plugin development so external storage can be used consistently across container orchestrators.