You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Podman API daemon handles the /images/create endpoint differently than Docker. The documentation specifies two parameters where the tag can appear when pulling an image:
fromImage - Name of the image to pull. The name may include a tag or digest.
tag - Tag or digest. If empty when pulling an image, this causes all tags for the given image to be pulled.
It is not clear to me whether it is a violation of the API to include the tag in both places or, if it is not, what the expected behavior is. When it is specified in both places, Podman fails to normalize the name to a valid format, whereas Docker is more graceful. Docker just takes the value from tag, potentially overriding any value in fromImage (treating ?fromImage=image%3Aanything&tag=latest the same as ?fromImage=image&tag=latest).
Podman handles /images/create better when fromImage and Tag are
specified. Now the tag/digest value provided in Tag will replace the one
in fromImage
Fixes: containers#23938
Signed-off-by: Nicola Sella <[email protected]>
Issue Description
The Podman API daemon handles the
/images/create
endpoint differently than Docker. The documentation specifies two parameters where the tag can appear when pulling an image:fromImage
- Name of the image to pull. The name may include a tag or digest.tag
- Tag or digest. If empty when pulling an image, this causes all tags for the given image to be pulled.It is not clear to me whether it is a violation of the API to include the tag in both places or, if it is not, what the expected behavior is. When it is specified in both places, Podman fails to normalize the name to a valid format, whereas Docker is more graceful. Docker just takes the value from
tag
, potentially overriding any value infromImage
(treating?fromImage=image%3Aanything&tag=latest
the same as?fromImage=image&tag=latest
).Steps to reproduce the issue
Describe the results you received
Nothing was pulled because the image name got normalized to an invalid format:
The daemon logs the following:
Describe the results you expected
I would expect this this unusual use of the API to be handled more gracefully, like Docker does:
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Fully updated Rocky Linux 9.4 on an ESXi-hosted VM.
Additional information
Issue manifests with Kestra (issue 4845).
The text was updated successfully, but these errors were encountered: