Volumes

Volumes lists your volumes with their size, with filters for driver, stack, unused and managed volumes.

• Create Volume makes a new volume.
• Files opens the volume's data in the File Manager.
• Backups says whether backups cover the volume and why not, lists its backups and restores them (see Backups). A volume a stack uses is backed up with that stack; the tab names the stack and shows its recent runs when the last one didn't back it up completely.
• Migrate copies it to another server (see Migrations).
• Remove deletes the volume and its data. Type its name to confirm. A volume in use, or one of a Docker Manager stack, can't be removed here. Its backups stay; with Remove Backups of Deleted Stacks and Volumes they go the set number of days later (see Backups).

A volume's Labels card also lists its Compose labels: labels set in a stack's compose.yaml after the volume was created. Docker Manager honors them for backups and maintenance (see Backups).

Sizes refresh about every minute; below the list you see when they were measured, and a volume's page shows it under its size. A size stays visible while a newer one is computed, with a small spinner beside it; Docker Manager keeps the last sizes while you use it, so coming back to the list doesn't wait for them again. On large volumes the first size can take a few minutes, and a spinner shows until then. If a measurement fails, the last sizes stay with a note that they may be out of date. A volume created since the last measurement shows "—" until the next one ("Not measured yet"). Volumes Docker doesn't measure, such as those of other drivers, show "—" too.

Only local volumes that keep their data in Docker's own volume folder can be browsed. Others show as Read-Only with the reason: volumes of other drivers or on remote storage such as NFS or CIFS, volumes that keep their data in memory or in a server folder (o=bind), and volumes Docker mounts from a device. Backups don't cover them either, except a volume that keeps its data in a server folder: it is backed up once that folder is allowed (a folder inside the stacks folder needs no allowing) and overlaps no other data; what backups leave out is listed in Backups. Docker Manager's own volumes can't be browsed, backed up, migrated or removed.

To remove several volumes, select their rows and press Remove. You see what is removed and what is left out before you confirm; if a removal fails, the closing message says why and stays until you close it.

Prune Volumes removes unused ones (see Maintenance).