• 916 Views

Not able to login on registry - Same happen on EX200 exam also

Hi ,
I am unable to login on images registry on LAB environment and same happened on EX200 exam also. It is working with servera.
Have to retake exam and schedule this week.
Could you someone help me asap and let me know what is wrong and how to fix it.Podman login issuePodman login issue

4 Replies
marisadean
Mission Specialist
Mission Specialist
  • 847 Views

Re: Not able to login on registry - Same happen on EX200 exam also

For docker the fix is to create /etc/docker/daemon.json and add

{ "insecure-registries" : ["lab.example.com:5443"] }

 then restart docker

See if the same works with podman? the filename might be different...

0 Kudos
Reply
Loading...
Yeni84
Flight Engineer
Flight Engineer
  • 797 Views

Re: Not able to login on registry - Same happen on EX200 exam also

@PALANIVELRAJAN Hello. Did you manage to find the solution to your problem? It would be interesting to let us know. Thank you.

0 Kudos
Reply
Loading...
aldidi
Cadet
Cadet
  • 493 Views

Re: Not able to login on registry - Same happen on EX200 exam also

logout and after login from server with ssh user_to_create_pod@server

0 Kudos
Reply
Loading...
Tracy_Baker
Starfighter Starfighter
Starfighter
  • 488 Views

Re: Not able to login on registry - Same happen on EX200 exam also

Read what it says at the end. "x509: certificate signed by unknown authority."

You can use this option with podman login and podman pull to get past this error:

--tls-verify=false

It also means that you cannot pull an image using podman run because the option doesn't exist with that command. So, in this case, use podman pull first, then podman run

-----

@marisadean's solution really wouldn't work because docker isn't used.

However, something similar exists for Podman. Edit the /etc/containers/registries.conf file and, in the [registries.insecure] section (which will probably need to be uncommented) add this line:

registries = [registry.lab.example.com]

You may also want to check for the existence of this file:  ~/.config/containers/storage.conf

If it exists for your user, it overrides /etc/containers/registries.conf. In this case, you'll want to make the changes to [registries.insecure] in it (also?).

-----

If you took Red Hat's RH134 class, this information is covered in Chapter 13, section 5 - in the Configuring Container Registries and Registry Security sections.

Program Lead at Arizona's first Red Hat Academy, est. 2005
Estrella Mountain Community College
0 Kudos
Reply
Loading...
Join the discussion
You must log in to join this conversation.