-
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
docker api: ContainerList does not seem to recognize filter arguments #9544
Comments
ContainerList
does not seem to recognize filter arguments
@baude PTAL |
Seems to work for me with upstream main.
|
did you try it through the docker-sdk? I get empty results there. Btw, why is there a |
@rmohr No I didnt try it through the docker sdk. I don't have time for that. The |
A friendly reminder that this issue had no activity for 30 days. |
Since we got no more feedback, I will assume this is fixed in the main branch. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When applying a filter to
ContainerList
, I don't get the expected containers returned.Steps to reproduce the issue:
Call podman with the docker sdk like this:
Describe the results you received:
I get no containers with prefix
prefix*
back. The result is empty.Describe the results you expected:
Against the docker daemon I get all containers starting with
prefix
returned.For instance, if prefix has the value
test
, I would expect that I get containers like this back :test1
,test-something
.Note that
VolumeList
it returns the expected results.Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):developer version
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: