-
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
podman images -q <image@digest> not working like docker #18445
Comments
This also seems to be an issue with the filter as well:
But podman:
And just for clarity, tags do work:
|
A friendly reminder that this issue had no activity for 30 days. |
@vrothberg This looks like a bug in containers/common/libimage? |
Looks like libimage is ignoring digest when accessed by reference? |
Thanks for reaching out, @KCSesh! I will take a look. |
I opened containers/common#1503 to fix the issue. |
Make sure that reference filters properly work on digests as well. To keep things simple, try to lookup an image for the user-specified value and compare IDs. This will implicitly fix #containers/podman/issues/18445 and probably more (unknown) issues. Fixes: #containers/podman/issues/18445 Signed-off-by: Valentin Rothberg <[email protected]>
Make sure that reference filters properly work on digests as well. To keep things simple, try to lookup an image for the user-specified value and compare IDs. This will implicitly fix #containers/podman/issues/18445 and probably more (unknown) issues. Fixes: #containers/podman/issues/18445 Signed-off-by: Valentin Rothberg <[email protected]>
A friendly reminder that this issue had no activity for 30 days. |
This is supposed to be fixed in podman 4.6 or at least in the main branch, I believe. |
Issue Description
podman images -q image@digest not working like docker does.
Steps to reproduce the issue
Steps to reproduce the issue
podman images --digests
podman images -q docker.io/library/ubuntu@sha256:0b8a884ad7ed20e50a68108895a6e7db54b303ad73b22b6b9ff5f60740dc03e2
<No output>
Describe the results you received
No output of image id
Describe the results you expected
Output of the image id
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
AWS EC2 instnace
Additional information
No response
The text was updated successfully, but these errors were encountered: