mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-10-12 08:57:42 +00:00
6140369208
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> |
||
|---|---|---|
| .. | ||
| testdata | ||
| config.go | ||
| df.go | ||
| docker_registry_options.go | ||
| errors.go | ||
| filters.go | ||
| image.go | ||
| image_test.go | ||
| layer_tree.go | ||
| manifests.go | ||
| parts.go | ||
| parts_test.go | ||
| prune.go | ||
| pull.go | ||
| pull_test.go | ||
| search.go | ||
| signing_options.go | ||
| tree.go | ||
| utils.go | ||