The new prune commands are potentially dangerous and I find it hard to predict what actually would be deleted. The user might use docker system df and docker image ls --filter dangling=true to get to this information, but this seems like an unneccessary step.
I propose to add a new operating mode where the normal output is produced without actually deleting the objects.
$ docker system prune --dry-run
Warning: Running in dry run mode, not actually deleting anything.
Deleted Volumes:
dockerdev-go-pkg-cache-gopath
dockerdev-go-pkg-cache-goroot-linux_amd64_netgo
Total reclaimed space: 112.1 MB
The user could then decide to run the same command again without --dry-run.
The new
prunecommands are potentially dangerous and I find it hard to predict what actually would be deleted. The user might usedocker system dfanddocker image ls --filter dangling=trueto get to this information, but this seems like an unneccessary step.I propose to add a new operating mode where the normal output is produced without actually deleting the objects.
$ docker system prune --dry-run Warning: Running in dry run mode, not actually deleting anything. Deleted Volumes: dockerdev-go-pkg-cache-gopath dockerdev-go-pkg-cache-goroot-linux_amd64_netgo Total reclaimed space: 112.1 MBThe user could then decide to run the same command again without
--dry-run.