diff options
| author | Valentin Rothberg <rothberg@redhat.com> | 2021-02-12 17:23:01 +0100 |
|---|---|---|
| committer | Valentin Rothberg <rothberg@redhat.com> | 2021-02-12 17:23:01 +0100 |
| commit | adfcb74602dcefb64fad226d4f949e5ee98ea324 (patch) | |
| tree | b586f60a9a343574f85074c1216d56e7ee9965ea /pkg/bindings/generate/generate.go | |
| parent | 1b284a298c0bde20561321f325d4a7ad00e7bd25 (diff) | |
| download | podman-adfcb74602dcefb64fad226d4f949e5ee98ea324.tar.gz podman-adfcb74602dcefb64fad226d4f949e5ee98ea324.tar.bz2 podman-adfcb74602dcefb64fad226d4f949e5ee98ea324.zip | |
make layer-tree lookup errors non-fatal
Internally, Podman constructs a tree of layers in containers/storage to
quickly compute relations among layers and hence images. To compute the
tree, we intersect all local layers with all local images. So far,
lookup errors have been fatal which has turned out to be a mistake since
it seems fairly easy to cause storage corruptions, for instance, when
killing builds. In that case, a (partial) image may list a layer which
does not exist (anymore). Since the errors were fatal, there was no
easy way to clean up and many commands were erroring out.
To improve usability, turn the fatal errors into warnings that guide the
user into resolving the issue. In this case, a `podman system reset`
may be the approriate way for now.
[NO TESTS NEEDED] because I have no reliable way to force it.
[1] https://github.com/containers/podman/issues/8148#issuecomment-778253474
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'pkg/bindings/generate/generate.go')
0 files changed, 0 insertions, 0 deletions