Bug 1846629
| Summary: | [RFE] Enable "podman search" to use wildcard (star) for queries | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Phil Jasbutis <pjasbuti> |
| Component: | podman | Assignee: | Valentin Rothberg <vrothber> |
| Status: | CLOSED ERRATA | QA Contact: | Alex Jia <ajia> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.2 | CC: | ajia, bbaude, ddarrah, dornelas, dwalsh, imcleod, jligon, jnovy, kanderso, lsm5, mheon, mitr, tsweeney, vrothber, ypu |
| Target Milestone: | rc | Keywords: | FutureFeature, Reopened |
| Target Release: | 8.4 | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | podman 2.2 or newer | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-16 14:21:45 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1186913, 1823908 | ||
|
Description
Phil Jasbutis
2020-06-12 11:04:32 UTC
Hi Valentin, the request is just about the usage of * as single character after the trailing slash like this $ podman search registry.redhat.io/* $ podman search registry.access.redhat.com/* This is not requested: $ podman search registry.redhat.io/rh*l $ podman search registry.access.redhat.com/rh*l With https://github.com/containers/libpod/commit/b05888a97dbb45a205ff535538ecdd91a19c6ae3 merged upstream, the next release of Podman will support wildcards. In fact, Podman will send any input search term to the registry and lets the registry decide whether it supports the term or not. As this RFE has been addressed with this PR: https://github.com/containers/libpod/pull/6621 and it will be part of the first version of Podman after Podman v2.0.0 (Likely the next version will be v2.0.1), I'm closing this PR as next release. Verified on podman-2.2.1-2.module+el8.3.1+9107+df0d2892.x86_64 w/ runc-1.0.0-69.rc92.module+el8.3.1+9107+df0d2892.x86_64. # podman search registry.access.redhat.com/*| grep rhel-tools redhat.com registry.access.redhat.com/rhel7/rhel-tools Provides the core systems administrator and ... 0 # podman search registry.redhat.io/*|wc -l 26 # podman search registry.redhat.io/"*"|wc -l 26 # podman search registry.access.redhat.com/*|wc -l 26 # podman search registry.access.redhat.com/"*"|wc -l 26 # podman search registry.redhat.io/rhel*|wc -l 26 # podman search registry.redhat.io/rhel7/*|wc -l 26 # podman search registry.redhat.io/rhel7/rhel*|wc -l 5 Need to confirm for the following testing. 1. can't find related image like registry.redhat.io/rhel7/rhel and registry.redhat.io/rhel7/rhel-tools # podman search registry.redhat.io/rhel7/rh*l|wc -l 0 # podman search registry.redhat.io/rhel7/rhel-t*|wc -l 0 2. got incorrect output # podman search registry.redhat.io/rhel7/rhel-to* INDEX NAME DESCRIPTION STARS OFFICIAL AUTOMATED redhat.io registry.redhat.io/rhel7-rhel-minimal Red Hat Enterprise Linux Minimal Image is a ... 0 redhat.io registry.redhat.io/rhel7/rhel-tools Provides the core systems administrator and ... 0 redhat.io registry.redhat.io/rhel7/rhel This platform image provides a minimal runti... 0 redhat.io registry.redhat.io/rhel7/rhel-atomic Red Hat Enterprise Linux Atomic Image is a m... 0 Any updates for '2. got incorrect output' in Comment 21? thanks! *shrug* using raw access like > curl 'https://registry.redhat.io/v1/search?n=25&q=rhel7/rhel-to*' | python -mjson.tool I see similar output (rhel-t* does not find rhel-tools, but rhel-to* does find both rhel-tools and rhel). So as far as Podman is concerned, this is consistent with comment#4 and comment#8. Why does the registry behave this way is an interesting question, but one that should be filed separately against the registry. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:0531 |