Podman image prune is removing images used in a image manifest, leaving the manifest behind.

[rhatdan]

Issue Description

Create an image with podman build
$ cat Containerfile
from alpine
run echo hi

$ podman build /tmp/
STEP 1/2: FROM alpine
STEP 2/2: run echo hi
--> Using cache 8907335901b513e5d774cc22eaf53c08493212070bd81cb1347228f589c4186f
--> 8907335901b5
8907335901b513e5d774cc22eaf53c08493212070bd81cb1347228f589c4186f

$ podman manifest create test 8907335901b513e5d774cc22eaf53c08493212070bd81cb1347228f589c4186f
$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/test latest 3b57a39f5d5e 33 seconds ago 604 B
8907335901b5 About a minute ago 8.13 MB
$ podman image prune
WARNING! This command removes all dangling images.
Are you sure you want to continue? [y/N] y
8907335901b513e5d774cc22eaf53c08493212070bd81cb1347228f589c4186f

This image is not dangling, it is being used by the manifest.

Steps to reproduce the issue

Steps to reproduce the issue
1.
2.
3.

Describe the results you received

Describe the results you received

Describe the results you expected

Describe the results you expected

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[rhatdan]

This stems from podman images --filter dangling=true listing the image.