[Podman] Re: Q: Slightly uncomplicating manifest-lists

All, Recently I wrote a blog article that touches on a few podman (and buildah) commands which are bound to catch people off-guard: https://podman.io/blogs/2021/10/11/multiarch.html Unfortunately the reason for the "Ugh! What? Really?" of 'rm' and 'push' is "maintaining compatibility" - hence, unlikely to change.  See https://github.com/containers/podman/issues/11899 So my thinking was, if we can't change the CLI can we make the feedback to users better?  At least then, people would be alerted when it comes to surprising 'rm'/'push' behavior.  For example: $ podman images REPOSITORY                 TAG         IMAGE ID      CREATED  SIZE docker.io/library/redis    latest      7faaec683238  7 days   116 MB reg.fed.org/fedora         34          191682d67252  2 weeks  184 MB ex.co/foo/bar              latest   [M]123456576b54  1 second 123 GB reg.acc.red.c/ubi8-init    latest      670b0e87da3c  4 weeks  251 MB quay.io/libpod/alpine      latest      961769676411  2 years  5.85 MB Indicating 'ex.co/foo/bar' is a manifest list not a regular image, and so needs special handling by the user.  Alternatively it could be it's own column.  I was just wanted to be sensitive to anyone who may be scraping the space-separated data for some purpose. What are your opinions/concerns/alternatives for something like this?