Daemon storage backends (containerd image store and storage drivers): How the daemon stores image layers and container writable layers on disk. ... For information about how Docker stores images and …

Managing volumes ... Try it out ... Use volumes Download and install Docker Desktop. Start a container using the Postgres image with the following command:

Docker Engine 29.0 and later uses the containerd image store by default for fresh installations. ... For information about the containerd image store, see containerd image store.

Docker Documentation is the official Docker library of resources, manuals, and guides to help you containerize applications.

Learn how to create, manage, and use volumes instead of bind mounts for persisting data generated and used by Docker.

See all storage options for each storage driver in the daemon reference documentation ... How the zfs storage driver works ... Image and container layers on-disk ... Image layering and sharing ... How …

When using the containerd image store (the default for Docker Engine 29.0 and later on fresh installations), image contents and container snapshots are stored in /var/lib/containerd.

Additional resources To learn more about the containerd image store and its capabilities in Docker Desktop, see containerd image store on Docker Desktop.

Docker's btrfs storage driver stores every image layer and container in its own Btrfs subvolume or snapshot. The base layer of an image is stored as a subvolume whereas child image layers and …

Configure the windowsfilter storage driver ... See windowsfilter options. ... You can change the storage location by configuring the data-root option in the Daemon configuration file: