-
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
RFC: podman prune images
by default should only delete dangling images
#2192
Comments
@baude Could you look at this? |
I think this might be intended behavior? Maybe this should be gated by a flag, separate from "remove leftover intermediate images"? |
That is not my interpretation of the help text:
To me |
FWIW, my thinking was prune should be removing any images with a tag and leaving the rest alone. |
Ugh, love md4 sometimes in GitHub. "images with a tag" s/b "images with a |
Nope, to be compatible with docker, prune removes all unused images (images that are not being used by a container). the atomic cli prune command was just the none images. the help text is incorrect and should be updated. you can see in the short description, it says unused. |
Correct the help text for the image prune command to state that it removes all unused images. Issue: containers#2192 Signed-off-by: baude <bbaude@redhat.com>
how do we get that functionality ^^ - that's what I'm interested in |
what do you want the command line switch to be? it should probably be somethign like --only-something-or-another |
podman image prune
seems to delete all imagespodman prune images
needs a switch to delete only none
images
Hmmm, I'm looking at: https://docs.docker.com/engine/reference/commandline/image_prune/ and it says:
Where danglng errors have the |
fine thats seems to be what we should do. |
podman prune images
needs a switch to delete only none
imagespodman prune images
by default should only delete dangling images
we now, by default, only prune dangling images. if --all is passed, we prune dangling images AND images that do not have an associated containers. also went ahead and enabled the podman-remote image prune side of things. Fixes: containers#2192 Signed-off-by: baude <bbaude@redhat.com>
we now, by default, only prune dangling images. if --all is passed, we prune dangling images AND images that do not have an associated containers. also went ahead and enabled the podman-remote image prune side of things. Fixes: containers#2192 Signed-off-by: baude <bbaude@redhat.com> MH: Removed dependence on remote-client adapter work to limit scale of changes Signed-off-by: Matthew Heon <matthew.heon@pm.me>
/kind bug
Description
possibly a variant of #1154.
podman image prune
seems to remove all images, not just unnamed images.podman version/info
The text was updated successfully, but these errors were encountered: