-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Impossible to delete an image #15006
Comments
Check with |
Yes, |
@slemeur did using It can happen that a so-called "build container" from |
Yes, I think it's exactly what happened indeed.
with the --force option, I have been able to delete it.
Thanks for helping out!
…On Thu, Aug 4, 2022 at 2:25 PM Valentin Rothberg ***@***.***> wrote:
@slemeur </~https://github.com/slemeur> did using --force resolve the issue?
It can happen that a so-called "build container" from podman build is
still hanging around and using the image. This may happen when, for
instance, a build gets killed.
—
Reply to this email directly, view it on GitHub
<#15006 (comment)>,
or unsubscribe
</~https://github.com/notifications/unsubscribe-auth/AAMPTIKYU5NRVOBNS7ZBWJDVXOZD5ANCNFSM54G2LRUA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Glad to be of help. I was about to close the issue but I think we can improve the error message to guide users to force-removing images in that case. |
Removing the |
Trying to remove an image that is in use by containers is a confusing experience for users who may not be aware of "external" containers which are not displayed in `podman ps` by default (see containers/podman/issues/15006). Add some context to the error from containers/storage to guide the user into listing external containers and force-removing the image. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Improve the error message when attempting to remove an image that is in use by an external/build container. Prior, the error only indicated that the image was in use but did not aid in resolving the issue. Fixes: containers#15006 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
/kind bug
Description
I have an image that I can't delete because Podman says it's currently in use by a container which does not exist.
Steps to reproduce the issue:
Unfortunately, I'm not sure how I ended up in this situation.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman images
:Output of
podman rmi
:Output of
podman image inspect
:Output of
podman ps -a
:The text was updated successfully, but these errors were encountered: