[Feature request] Dry run mode for prune commands
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. ```bash $ 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`.
Posted by albers on Feb 1, 2017, 8:25 AM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
[Feature request] Dry run mode for prune commands
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. ```bash $ 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`.
Comments (0)
No comments yet. Start the discussion.