podman login command gives error:authenticating credentials

[BODALIA]

Looks like a simple question with a simple answer but it is not working for me in my VMware Rhel9 machine that I have set up. I have successfully installed container-tools, but am unable to log in to the container registry. I am using my username and password that I used to register the machine, the same as the one I use to log in to my course RHCSA Rapid Track

Can anyone help me please?

Thanks,

Usha

[Tess]

Alright! So, the first half of all that confirms that both your DNS and your Internet connection are in fact working correctly. That's good!

I also took the time to try your commands on my own RHEL box. 

That last command you type, also does not work for me. 

What does work for me is:

• podman search alpine

I will look into why the search you're doing doesn't work. The man-page says it should work for v2 registries, which this is... 

[Tess]

Darn, that wasn't it either. I need to curl the v2 URL with a / at the end.

% curl https://registry.access.redhat.com/v2/                  
{}% 

So, that URL works after all, but it returns a null set. 

EDIT: The stuff I posted here before is wrong afterall. 

Ha!! I've got it!

The problem is not you. The problem is with Red Hat! Their own registry is broken. 

Let's do that curl again!

$ curl https://registry.access.redhat.com/v2

You should be redirected automatically to target URL: https://crane.registry.redhat.com/v2/

This tells you that you are being redirected to crane.registry.redhat.com. 

Yeah, that server is unknown in DNS! 🤪

$ curl https://crane.registry.redhat.com/v2

curl: (6) Could not resolve host: crane.registry.redhat.com

[BODALIA]

Hi Tess,
Thank you so much for persevering and trying out my commands. You are absolutely right, my curl has also re-directed. But how do I still see/access the images from there? The below is what I’ve tried, but I know from my RedHat course RSCSA Rapid Track, that the podman search command with a / lists images in that registry that I can get choose to pull into my system. So, can you tell me what commands to run to get it to work please, as below still does not work; hence I am unable to use containers.
Kind regards,
Usha
******************************************************************************************
[podmgr@kingfisher user]$ curl https://registry.access.redhat.com/v2

Redirecting...

Redirecting...

You should be redirected automatically to target URL: https://crane.registry.redhat.com/v2/>. If not click the link.[podmgr@kingfisher user]$
[podmgr@kingfisher user]$ podman search crane.registry.redhat.com/
Error: 1 error occurred:
* couldn't search registry "crane.registry.redhat.com": pinging container registry crane.registry.redhat.com: Get https://crane.registry.redhat.com/v2/: dial tcp: lookup crane.registry.redhat.com on 192.168.83.2:53: read udp 192.168.83.133:59916->192.168.83.2:53: i/o timeout


[podmgr@kingfisher user]$ podman search crane.registry.redhat.com/v2/
Error: 1 error occurred:
* couldn't search registry "crane.registry.redhat.com": pinging container registry crane.registry.redhat.com: Get https://crane.registry.redhat.com/v2/: dial tcp: lookup crane.registry.redhat.com on 192.168.83.2:53: read udp 192.168.83.133:54019->192.168.83.2:53: i/o timeout


[podmgr@kingfisher user]$ podman search "crane.registry.redhat.com/v2/"
Error: 1 error occurred:
* couldn't search registry "crane.registry.redhat.com": pinging container registry crane.registry.redhat.com: Get https://crane.registry.redhat.com/v2/: dial tcp: lookup crane.registry.redhat.com on 192.168.83.2:53: read udp 192.168.83.133:60575->192.168.83.2:53: i/o timeout

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

[Fran_Garcia · Accepted solution]

I think the reference to crane.registry.redhat.com is misleading. I can just search and download images just fine:

➜ grep redhat.com /etc/containers/registries.conf
unqualified-search-registries = ["registry.fedoraproject.org", "registry.access.redhat.com", "docker.io", "quay.io"]

➜ podman login registry.access.redhat.com
Username: XXXX  <-- it's the same user/password I use for the RH Portal at https://access.redhat.com
Password:
Login Succeeded!

➜ podman search ubi | grep registry.access
registry.access.redhat.com/ubi8/go-toolset Platform for building and running Go 1.11.5...
registry.access.redhat.com/ubi9/go-toolset rhcc_registry.access.redhat.com_ubi9/go-tool...
registry.access.redhat.com/ubi8/openjdk-8-runtime OpenJDK 1.8 runtime-only image on Red Hat Un...
registry.access.redhat.com/ubi8/openjdk-11-runtime OpenJDK 11 runtime-only image on Red Hat Uni...

[...]

➜ podman pull registry.access.redhat.com/ubi9/ubi:latest
Trying to pull registry.access.redhat.com/ubi9/ubi:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 33b9f09cff46 done
Copying config e7236a3e07 done
Writing manifest to image destination
Storing signatures
e7236a3e070f267713ad79c451b8628166abc0bc9c855f624619e099ec3faa99

➜ curl -vi https://registry.access.redhat.com

➜ echo $?
0

➜ getent hosts registry.access.redhat.com
23.200.66.161 e40408.d.akamaiedge.net
23.200.66.155 e40408.d.akamaiedge.net

➜ podman logout registry.access.redhat.com
Removed login credentials for registry.access.redhat.com

➜ podman pull registry.access.redhat.com/ubi8-minimal:latest
Trying to pull registry.access.redhat.com/ubi8-minimal:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob d2b5f358ecf1 skipped: already exists
Copying config f4fb65011c done
Writing manifest to image destination
Storing signatures
f4fb65011c56d354c56b9d688b2da5bd1e887a0108fe0d7554c6a4c514d89cb4

[mansin99]

the issue is related to resolving the DNS.

If DNS issues persist, you can specify a custom DNS configuration for Podman by editing /etc/containers/containers.conf or /etc/containers/registries.conf and adding the dns entry under the [containers] section, also remove any other DNS entries.

[containers]
dns = ["8.8.8.8", "1.1.1.1"]

then sudo systemctl restart podman


this should resolve the issue