-
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
[Bug]: podman volume prune with !=
as filter does not work
#17051
Comments
We've been adding |
@jschintag Interested in opening a PR to implement this? |
Unfortunately, I haven't worked on podman before and I don't have time at the moment to get familiar with a new project. |
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from beeing pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from beeing pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
I can pick it up /assign |
Great thanks. |
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from beeing pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from beeing pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from beeing pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Should this be closed now that #17483 merged? |
Closing this. |
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from beeing pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from being pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from being pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Add a script to initialize secex-data volume during installation. This is achieved by having the tarball stored on a second disk. Also run a podman container that mounts the volume to keep it from being pruned. See: containers/podman#17051 Signed-off-by: Jan Schintag <[email protected]>
Issue Description
Using
podman volume prune
with a filter excluding specific volumes (e.g.label!=
orname!=
) fails.Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
All volumes except testvolume would be pruned (none in this case)
podman info output
The text was updated successfully, but these errors were encountered: