BODALIA
Mission Specialist
Mission Specialist
  • 7,831 Views

podman login command gives error:authenticating credentials

Jump to solution

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

Labels (1)
Tags (2)
1 Solution

Accepted Solutions
Fran_Garcia
Starfighter Starfighter
Starfighter
  • 3,495 Views

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

View solution in original post

21 Replies
Chetan_Tiwary_
Moderator
Moderator
  • 4,869 Views
Hi Usha,
Thanks for reaching out ! Which container registry you are trying to log in ?
0 Kudos
BODALIA
Mission Specialist
Mission Specialist
  • 4,856 Views
Hi Chetan,
from my vmware virtual terminal, I am running command
podman login registry.access.redhat.com

I read somewhere that authentication is not required for this registry but it still asks me, so I put in username ushakant, and the password that I use to login to my course. The error that I get is as follows:

Error: authenticating creds for "registry.access.redhat.com": pinging container registry registry.access.redhat.com: Get https://registry.access.redhat.com/v2/: dial tcp: lookup registry.access.redhat.com on 192.168.83.2:53: read udp 192.168.83.133:40892->192.168.83.2:53: i/o timeout

Thank you,
Usha


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
Tess
Flight Engineer
Flight Engineer
  • 4,646 Views

The error message you're getting is not about the credentials themselves.

It's telling you that your RHEL9 box cannot do a DNS lookup of the host you're telling it to find. So, it's time for basic troubleshooting. 

  1. Does your RHEL box have an Internet connection? 
  2. The message says that your DNS server is 192.168.83.2. Is that correct? How did you configure your networking?
  3. What's the outcome of "nslookup www.google.com"?
  4. What's the outcome of "ping www.google.com"?
  5. What's the outcome of "ping 8.8.8.8"?
Chetan_Tiwary_
Moderator
Moderator
  • 4,844 Views

What about the DNS and general curl  connectivity to the registry URL ( without podman login ) ?

0 Kudos
kash
Cadet
Cadet
  • 2,518 Views

what is the solution for this

 

0 Kudos
BODALIA
Mission Specialist
Mission Specialist
  • 4,851 Views

Hi Chetan, from my vmware virtual terminal, I am running command podman login registry.access.redhat.com I read somewhere that authentication is not required for this registry but it still asks me, so I put in username ushakant, and the password that I use to login to my course. The error that I get is as follows: Error: authenticating creds for "registry.access.redhat.com": pinging container registry registry.access.redhat.com: Get https://registry.access.redhat.com/v2/: dial tcp: lookup registry.access.redhat.com on 192.168.83.2:53: read udp 192.168.83.133:40892->192.168.83.2:53: i/o timeout Thank you,

0 Kudos
Tess
Flight Engineer
Flight Engineer
  • 4,834 Views

I could have sworn that I posted a response in this thread. Don't know why it's gone

The error message you're getting indicates a network problem, not one of authentication. 

The message says you're trying to DNS lookup against 192.168.83.2. Is that really the DNS server for your Redhat box? Please verify your network configuration, because your Redhat box cannot reach your DNS server. 

0 Kudos
BODALIA
Mission Specialist
Mission Specialist
  • 4,817 Views

Hi Tess,

thank you for your response. I have done the following as I suspected that too.

nmcli con add con-name new-con ifname ens160 type ethernet ipv4.method manual ipv4.addresses 192.168.83.133/24 ipv4.gateway192.168.83.2 ipv4.dns192.168.83.2 connection.autoconnect yes

nmcli con up new-con

nmcli con mod ens160 connection.autoconnect no 

nmcli con show....gives the following

NAME UUID TYPE DEVICE
new-con 89453323-c2ee-4a0f-a7fa-699b59daf26f ethernet ens160

I also reinstalled and restarted httpd, which started on port 80

and to make sure I ran

firewall-cmd --add-service http; firewall-cmd --add-port 80/tcp --permanent; firewall-cmd --reload

Please see output now. I still can not login to registry.access.redhat.com, when I run podman login --get-login it tells me it is not logged in. I used the same dns ipaddress that came with the orginal network connection that was set up when I installed Linux V9 - and ping works

BODALIA_0-1686758534271.png

 

 

0 Kudos
Tess
Flight Engineer
Flight Engineer
  • 4,812 Views

Many of the things you're describing have zero, no relation whatsoever, with podman login to a remote registry. Having a httpd running locally, or having the firewall open to your own httpd is not related at all. 

But, it's good that you included your screenshot, because it makes me realize something I'd overlooked: you're running RHEL inside a VMWare Fusion VM on MacOS. 

So now we know which aspects to troubleshoot. 

  1. Why are you manually configuring the NIC of your RHEL VM? VMWare Fusion could be giving all the required settings via DHCP.
  2. Since you're manually setting the configuration, are you sure these settings are correct? How do you know these settings are correct? 
  3. What settings have you applied to the virtual NIC of the VM in VMWare? Did you set it to NAT? To bridged? Or even host-only? 

 

EDIT: 

Your screenshot does not actually show the error message that you quoted earlier. In fact, your screenshot suggests that there is a working network connection. 

So can you confirm that you can correctly:

??

0 Kudos
Join the discussion
You must log in to join this conversation.