Closed srcshelton closed 4 years ago
Thanks for opening the issue! We're tracking the topic already over in https://github.com/containers/podman/issues/6288, so I am going to close this one here. Feel free to join the conversation over in https://github.com/containers/podman/issues/6288.
A friendly reminder that this issue had no activity for 30 days.
This issue was supposed to be closed.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman is incredibly slow at listing images:
... which is about half a second per image.
The host system has 4 enterprise spinning disks in a RAID-6 array, with the filesystems podman is using residing on LVM volumes... so this shouldn't be too much of a bottleneck.
Can the amount of data that podman needs to interrogate per image be reduced (perhaps the image size could be hidden by default if this has to be computed on the fly)? On the other hand, doing
time podman image ls -q
to show only the digests also took1m18.990s
, so it looks as if data is being computed regardless of the output filter - or the the delay lies elsewhere.Alternatively, could podman maintain a cache or database of image attributes which is kept updated internally, allowing image listing to be near-instantaneous?
(Listing a specific image, e.g.
podman image ls docker
is much faster... but sometimes a view of all images is needed).Output of
podman version
:Output of
podman info --debug
: