Docker API image queries returning differing Id values #11623
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
The Docker-compatible Unix sock api seems too provide differing values for the Id field between
/images/json
and/images/<imageName>/json
. The latter includes the "sha256:" prefix while the latter does not. Docker itself seems to use the prefix in both cases. Apologies if I'm using incorrect terms or I'm obviously wrong about this one, it just seemed a bit unusual to me.Steps to reproduce the issue:
Pull any image (quay.io/bitnami/nginx in my case)
Run
curl -s --unix-socket /run/podman/podman.sock http://v1.24/images/json
and observe the Id valueRun
curl -s --unix-socket /run/podman/podman.sock http://v1.24/images/someimagename/json
and observe its Id valueDescribe the results you received:
For
/images/json
:For
/images/someimagename/json
:Describe the results you expected:
I expected that both of the Id values would have the
sha256:
prefix, or would at least match.The output from Docker is:
For
/images/json
For
/images/someimagename/json
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)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
I tested this both on a Mac as well as a linux laptop running Arch.
The text was updated successfully, but these errors were encountered: