podman/libpod/image
Matthew Heon 3e92bcbf71 Do not prune images being used by a container
Podman is not the only user of containers/storage, and as such we
cannot rely on our database as the sole source of truth when
pruning images. If images do not show as in use from Podman's
perspective, but subsequently fail to remove because they are
being used by a container, they're probably being used by Buildah
or another c/storage client.

Since the images in question are in use, we shouldn't error on
failure to prune them - we weren't supposed to prune them in the
first place.

Fixes: #3983

Signed-off-by: Matthew Heon <matthew.heon@pm.me>
2019-09-10 13:30:50 -04:00
..
testdata Split refNamesFromImageReference from Runtime.getPullListFromRef 2018-08-01 18:22:58 +00:00
docker_registry_options.go image: add user agent to Docker registry options 2019-08-12 18:28:36 +03:00
errors.go add podman container|image exists 2018-11-26 09:19:39 -06:00
image.go image: remove unused Decompose method 2019-08-28 08:59:33 -05:00
image_test.go add --pull flag for podman create&run 2019-08-09 15:21:34 -04:00
parts.go Remove imageParts.{isTagged,registry,name,tag} 2019-01-14 04:07:24 +01:00
parts_test.go Remove imageParts.{isTagged,registry,name,tag} 2019-01-14 04:07:24 +01:00
prune.go Do not prune images being used by a container 2019-09-10 13:30:50 -04:00
pull.go Fix directory pull image name for OCI images 2019-08-19 12:49:59 +02:00
pull_test.go Use imageParts.referenceWithRegistry in pullGoalFromPossiblyUnqualifiedName 2019-01-14 04:07:23 +01:00
search.go fix search output limit 2019-08-01 16:15:15 -04:00
signing_options.go Stage3 Image Library 2018-03-14 20:21:31 +00:00
utils.go podman-remote save [image] 2019-02-20 12:58:05 -06:00