On 10/19/21 11:54, Chris Evich wrote:
> Recently I wrote a blog article that touches on a few podman (and
> buildah) commands which are bound to catch people off-guard:
> Unfortunately the reason for the "Ugh! What? Really?" of 'rm' and
> 'push' is "maintaining compatibility" - hence, unlikely to change. See
> 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?
We should add the field to the end of list.
REPOSITORY TAG IMAGE ID CREATED SIZE TYPE
docker.io/library/redis latest 7faaec683238 7 days 116 MB Image
reg.fed.org/fedora 34 191682d67252 2 weeks 184 MB Image
ex.co/foo/bar latest [M]123456576b54 1 second 123 GB List
reg.acc.red.c/ubi8-init latest 670b0e87da3c 4 weeks 251 MB Image
quay.io/libpod/alpine latest 961769676411 2 years 5.85 MB Image
I like that.
For the sake of exploring an alternative: we could further separate images and lists. podman-images would only list images, and podman-manifest-ls (does not exist yet) would only list manifests.
Podman mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org