cancel
Showing results for 
Search instead for 
Did you mean: 
  • 663 Views

Chapter 14 s05 cannot podman login or pull registry

Jump to solution

I get the following error when trying to get the container image from the registry registry.lab.example.com

 

tls: failed to verify certificate: x509: certificate relies on legacy Common Name field, use SANs instead

 

Is there a bug in the lab?

 

 

 

registry.lab.example.com

1 Solution

Accepted Solutions
87951469
Flight Engineer
Flight Engineer
  • 80 Views

RESOLVED. 

issue: attempting to "podman run ...." as root@serverb will cause this issue. 

as per solution: podsvc@serverb can "podman run ...." without any issues. 

View solution in original post

5 Replies
Chetan_Tiwary_
Community Manager
Community Manager
  • 642 Views

@anonymous3 I dont think so there is a bug in the lab - can you recreate your lab and retry the same lab exercise ?

0 Kudos
87951469
Flight Engineer
Flight Engineer
  • 98 Views

Im getting the exact same error. 

87951469
Flight Engineer
Flight Engineer
  • 97 Views

Error: 

Trying to pull registry.lab.example.com/rhel9/httpd:24:latest... 
Error: initializing soruce docker://registry.lab.example.com/rhel9/httpd-24:latest: pinging container registry registry.lab.example.com: Get "https://registry.lab.example.com/v2/": tls: failed to verify certificate: x509 certificate relies on legacy COmmon Name filed, use SANs instead. 

87951469
Flight Engineer
Flight Engineer
  • 81 Views

RESOLVED. 

issue: attempting to "podman run ...." as root@serverb will cause this issue. 

as per solution: podsvc@serverb can "podman run ...." without any issues. 

Chetan_Tiwary_
Community Manager
Community Manager
  • 73 Views

@87951469 glad that you figured out the issue with the user with which you are running the podman run command. 

Now this is what we call troubleshooting ! kudos ! 

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