diff options
author | Ed Santiago <santiago@redhat.com> | 2020-02-19 13:30:12 -0700 |
---|---|---|
committer | Ed Santiago <santiago@redhat.com> | 2020-02-20 07:55:29 -0700 |
commit | 29930fae702ee5aea62353a14dce26d5e93a27db (patch) | |
tree | cdfe26d898e6eee8f354e0ca2f0aa76b41ced437 /docs | |
parent | 126f75d7be3353c2df7ed1c3f9c6e0a7b707422e (diff) | |
download | podman-29930fae702ee5aea62353a14dce26d5e93a27db.tar.gz podman-29930fae702ee5aea62353a14dce26d5e93a27db.tar.bz2 podman-29930fae702ee5aea62353a14dce26d5e93a27db.zip |
podman images: add --filter=since=XX
Looks like a bit of a misunderstanding from early on.
Docker implements --filter=since=IMAGE. Podman implements 'after'
instead of 'since'. Add an equivalent case statement to handle
both, keeping 'after' because we have no way of knowing if it
is used in the field.
Update documentation ... and fix what looks like a complete
misinterpretation of what the code actually does: the man page
claimed that these were time fields, but I don't see any
possible incantation in which a time value works or could
work. Updated docs to reflect IMAGE usage. Also changed
nonworking '==' to single '='.
Added tests. [UPDATE: skip with broken podman-remote]
Fixes: #5040
Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/source/markdown/podman-images.1.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/source/markdown/podman-images.1.md b/docs/source/markdown/podman-images.1.md index d22fb940f..09778e3c2 100644 --- a/docs/source/markdown/podman-images.1.md +++ b/docs/source/markdown/podman-images.1.md @@ -29,11 +29,11 @@ Filter output based on conditions provided Filters: - **after==TIMESTRING** - Filter on images created after the given time.Time. + **since=IMAGE** + Filter on images created after the given IMAGE (name or tag). - **before==TIMESTRING** - Filter on images created before the given time.Time. + **before=IMAGE** + Filter on images created before the given IMAGE (name or tag). **dangling=true|false** Show dangling images. Dangling images are a file system layer that was used in a previous build of an image and is no longer referenced by any active images. They are denoted with the <none> tag, consume disk space and serve no active purpose. |