-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: Let podman volume prune
show the volumes that are going to be removed
#8913
Comments
Good idea. Interested in opening a PR? I think this would make sense for a few of the tools. Note that this could be a bit racy. |
Thanks. Sad but true I'm not able to open a PR. Because I'm not a developer and most of the source code I don't understand. I don't know go. So, I hope some Dev who is capable of implementing this would take over to get it done. I would be able to help testing the implementation, though. |
No problem, I set this as a good first issue, and we shall see if someone grabs it. Thanks for your suggestion, and any help you give to the project is appreciated. |
Hello, I am quite a beginner in open-source and completely new to the Podman project. |
@iwita I assigned the issue to you. Volume prune tests can be found here https://github.com/containers/podman/blob/master/test/e2e/volume_prune_test.go |
Hello, |
How about podman volume prune <<< n | grep VOLUMES |
You can do that as a system tests. test/system/*.bats |
@rhatdan Thank you very much for your help! |
/kind feature
Description
Running
podman volume prune
you have to confirm the operation but you don't see which volumes actually will be removed after you confirm the command:I was trapped by the issue #7862. This could have been avoided by showing the volumes that are going to be removed before you confirm the removal. Because the user would have the chance that there is a volume going to be removed that's currently in use by a running container instance. Possible data loss could be prevented this way.
Or at least add an option to the command that will show the volumes that are going to be removed.
Steps to reproduce the issue:
podman volume prune
Hit 'y'
Describe the results you received:
Describe the results you expected:
Output of
podman version
:Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: