-
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
Filter does not work for /networks REST API #9526
Comments
The filters have to be a |
@Luap99 thanks for pointing out. We are using |
I think this is a valid issue if docker still accept the old format we should allow this too. |
@Luap99 it will be great if podman can add this support. |
Docker allows both the old `map[string]map[string]bool` and the newer `map[string][]string` for the filter param so we should too. Fixes containers#9526 Signed-off-by: Paul Holzinger <[email protected]>
PR #9531 |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Filtering networks by name using REST API always returns an empty array. It works for docker.
Steps to reproduce the issue:
podman network create foo-a
curl -gG -sSLw "%{http_code}" --unix-socket /var/run/podman/podman.sock http://localhost/networks --data-urlencode 'filters={"name":{"foo-a":true}}'
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
CLI works:
podman network ls -f 'name=foo-a'
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: