1# gordon volumes
2
3List and clean up Docker volumes managed by Gordon.
4
5## Commands
6
7### `gordon volumes list`
8
9List all Gordon-managed volumes.
10
11```bash
12gordon volumes list
13gordon volumes list --json
14```
15
16| Flag | Description |
17|------|-------------|
18| `--json` | Output as JSON |
19
20### `gordon volumes prune`
21
22Remove app-owned volumes that were explicitly released and are no longer used by any container.
23
24```bash
25gordon volumes prune
26gordon volumes prune --dry-run
27gordon volumes prune --no-confirm
28```
29
30| Flag | Description |
31|------|-------------|
32| `--dry-run` | Report the plan without deleting |
33| `--no-confirm` | Skip confirmation prompt |
34| `--json` | Output as JSON |
35
36#### What survives
37
38A volume is removed only when all of the following hold:
39
40- A durable ownership record explicitly marks it `released`.
41- The runtime labels agree with that record: the app, the app incarnation UUID, and the service.
42- No container mounts it.
43
44Everything else survives. Attached and retained volumes, volumes carrying only `gordon.managed`, volumes with no Gordon provenance, and volumes whose ownership cannot be established all survive. Ownership is never inferred from the volume name, and labels alone never make a volume deletable.
45
46With current metadata no lifecycle marks a volume `released`, so a volume prune normally reports a zero-deletion success. The command still lists every candidate with its verdict and reason, and `--json` returns the same plan shape as `gordon images prune`.
47
48## Related
49
50- [Volumes Configuration](../config/volumes.md)
51- [Images](./images.md)