Files
podman/libpod/image
Valentin Rothberg 3752016338 podman rmi: handle corrupted storage better
The storage can easily be corrupted when a build or pull process (or any
process *writing* to the storage) has been killed.  The corruption
surfaces in Podman reporting that a given layer could not be found in
the layer tree.  Those errors must not be fatal but only logged, such
that the image removal may continue.  Otherwise, a user may be unable to
remove an image.

[NO TESTS NEEDED] as I do not yet have a reliable way to cause such a
storage corruption.

Reported-in: https://github.com/containers/podman/issues/8148#issuecomment-787598940
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
2021-03-01 09:52:03 +01:00
..
2020-01-28 13:36:10 -06:00
2020-12-22 13:34:31 -05:00
2021-02-22 09:03:51 +01:00
2021-02-22 09:03:51 +01:00
2021-01-22 20:19:13 +01:00
2020-12-22 13:34:31 -05:00
2021-02-22 09:03:51 +01:00
2020-11-13 15:40:06 +01:00
2021-02-22 09:03:51 +01:00
2018-03-14 20:21:31 +00:00
2020-02-17 11:12:35 +01:00
2021-02-22 09:03:51 +01:00