-
Notifications
You must be signed in to change notification settings - Fork 471
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
Docker wrapper doesn't remove image after task has finished #6196
Comments
@computezrmle, might this be the case #6051 ? |
For me this line doesn't make sense - at least for podman - since it creates an illegal remove command.
|
Sorry, mixed What remains is the fact that disk usage and number of images steadily grows. |
'podman image rm ' is the correct syntax. What happens when you run the command manually? |
Hm.
At first sight it suggests there are 4 unused images consuming 352 MB each. Will close this issue. |
Please verify.
If necessary please provide a patch.
Don't know if docker behaves differently.
At the end of my docker task logs (with podman) a command sequence like this can be found:
stop
seems to be OK.container rm
seems to be OKimage rm
doesn't seem to be OK (at least if podman is used).According to the podman manual
rm
removes containers whilermi
is the command to remove images.As a result unused images remain on the local storage until removed manually.
The text was updated successfully, but these errors were encountered: