-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volume filters are exclusive rather than inclusive #6765
Comments
So we don't lose context on the discussion, from: #6756 (comment)
|
A friendly reminder that this issue had no activity for 30 days. |
@mheon Can we close this issue? |
No, this is still an issue |
@ashley-cui PTAL |
@ashley-cui Any movement on this? |
When using multiple filters, return a volume that matches any one of the used filters, rather than matching both of the filters. This is for compatibility with docker's cli, and more importantly, the apiv2 compat endpoint Closes containers#6765 Signed-off-by: Ashley Cui <[email protected]>
Thanks for working on this @ashley-cui :) |
of course! :) |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Arguable?
Description
In #6756, I pointed out that volume filters appear to be exclusive rather than inclusive, which makes for a confusing result when using APIv2 to, e.g., retrieve multiple volumes with specified names.
Steps to reproduce the issue:
name
filter with multiple entries. Notice that no results are returned.Describe the results you received:
No results rather than multiple results for each volume matching a specified name.
Describe the results you expected:
As above.
Additional information you deem important (e.g. issue happens only occasionally):
Shell transcript:
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: