-
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
unbound reference filter pattern #11905
Comments
You say " but that seems to be fixed in recent versions." - you've tested on a more recent Podman (3.4.0 ideally)? Does it resolve the issue entirely, or only the reference not being a regular expression? If the issue is not present upstream and is only in RHEL, please close this an open a Bugzilla. |
the docs i mean, not the pattern itself. :) I'll check if the bug also is there when building from source. |
It's reproducible on main branch on Fedora 34.
Not sure where the
|
workaround: |
A friendly reminder that this issue had no activity for 30 days. |
This seems to be a factor in Docker hard coding the registry docker.io into the tool.
Now Podman could do something similar and walk through the registries and grab images that match or just look for images that end with a '/' and only match on the final image name. Docker only matches on the full image name.
|
If I manually add the glob, it works.
But only at the end.
|
Currently we match *reference*, which is incorrect. Docker hard codes the current registry and matches the reference exactly, allowing users to pass in globs. This fix will truncate the registry name and localhost/ as well has the constant library/ off of images and then attempt to match. Helps Fix: containers/podman#11905 Signed-off-by: Daniel J Walsh <[email protected]>
Currently we match *reference*, which is incorrect. Docker hard codes the current registry and matches the reference exactly, allowing users to pass in globs. This fix will truncate the registry name and localhost/ as well has the constant library/ off of images and then attempt to match. Helps Fix: containers/podman#11905 Signed-off-by: Daniel J Walsh <[email protected]>
Currently we match *reference*, which is incorrect. Docker hard codes the current registry and matches the reference exactly, allowing users to pass in globs. This fix will truncate the registry name and localhost/ as well has the constant library/ off of images and then attempt to match. Helps Fix: containers/podman#11905 Signed-off-by: Daniel J Walsh <[email protected]>
Currently we match *reference*, which is incorrect. Docker hard codes the current registry and matches the reference exactly, allowing users to pass in globs. This fix will truncate the registry name and localhost/ as well has the constant library/ off of images and then attempt to match. Helps Fix: containers/podman#11905 Signed-off-by: Daniel J Walsh <[email protected]>
Currently we match *reference*, which is incorrect. Docker hard codes the current registry and matches the reference exactly, allowing users to pass in globs. This fix will truncate the registry name and localhost/ as well has the constant library/ off of images and then attempt to match. Helps Fix: containers/podman#11905 Signed-off-by: Daniel J Walsh <[email protected]>
The previously inherited behavior from Podman was matching too aggressively. Now, the filter matches the exact behavior of Docker, simplifies the code and is tested directly in libimage. Context: containers/podman#11905 Signed-off-by: Valentin Rothberg <[email protected]>
The previously inherited behavior from Podman was matching too aggressively. Now, the filter matches the exact behavior of Docker, simplifies the code and is tested directly in libimage. Context: containers/podman#11905 Signed-off-by: Valentin Rothberg <[email protected]>
Update the `--filter reference=...` tests to reflect recent changes in c/common. The reference values now match as specified without implicitly adding wildcards arounds. Fixes: containers#11905 Signed-off-by: Valentin Rothberg <[email protected]>
The previously inherited behavior from Podman was matching too aggressively. Now, the filter matches the exact behavior of Docker, simplifies the code and is tested directly in libimage. Context: containers/podman#11905 Signed-off-by: Valentin Rothberg <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman images --filter reference=foo:
also matchafoo
images and there does not seem to be a way around that.(My manpage states
reference
is a RegEx, but it's actually a shell glob, otherwise^
might have helped; but that seems to be fixed in recent versions.)it seems to be due to this, which sets reference filter
*${reference}*
:https://github.com/containers/common/blob/32e20295f1c657cd304466a54868f60f7c8aaaa8/libimage/filters.go#L148
The
reference
filter was introduced for docker cli compat (#2266), but on Docker Desktop for Windows does not have this problem.Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
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
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
No, but source code suggests it's still the same.
Troubleshooting does not mention reference filter.
Additional environment details (AWS, VirtualBox, physical, etc.):
RHEL virtual machine in public cloud.
The text was updated successfully, but these errors were encountered: