Bearer token authorization fails
The original issue https://github.com/podman-desktop/podman-desktop/issues/9786 was filed by user on Podman-desktop repo. After looking at the details it seems it could be something that be explored in the podman repo
Initial bug description:
I'm trying to pull an image from our ai registry using a RegistryToken via a REST API call, which results in a "no such host" error. I have used the Docker compatibility mode as well as the Podman endpoint with the same result. The same call works with Docker Desktop. I have observed that the ai registry in the error message is not the one we are requesting. The Azure registry looks like this: ai-registry.XYZ.com The error message we get is: response={"message":"lookup ai-registry.ai-registry.XYZ.com: no such host"} The first part of the URL is duplicated somewhere, which probably leads to the "no such host" error.
Steps to reproduce
Podman Desktop and Podman Extension is up and running with Docker Compatibility Mode enabled Send Pull: -> Option1: Send Pull Request with RegistryToken via REST API call using the Docker API method CreateImageAsync of the IImageOperations interface -> Option2: use cmd: podman pull --creds ":RegistryToken" ai-registry.XYZ.com/image:tag
Further debugging from the user provided int his thread https://github.com/podman-desktop/podman-desktop/issues/9786#issuecomment-2533396058
Operating system
Windows 11 (22H2)
Installation Method
Installer from website/GitHub releases
Podman desktop Version
1.13.3
Podman version
5.2.5
Hello @rujutashinde , can you please try this with the latest podman v5.4.1 ?
Have informed the original bug authors to try to reproduce using podman v 5.4.1
Thanks a lot for following up on this! I will try reproduce with podman 5.4.1 this weekend and report back to you.
A friendly reminder that this issue had no activity for 30 days.