06-30-2026 06:01 AM
Hi,
Here's a polished rewrite:
Just wondering if anyone has come across an IBM Container Registry authentication issue where the registry traffic is routed through PaloAlto Akamai geo-location edge servers (for example,
cp.icr.io).I experienced intermittent authentication failures where the login process would hang and never complete. After some investigation, I found that adding a static entry for
cp.icr.io(pointing it to a specific IP address,xxx.xxx.xxx.xxx) resolved the issue and authentication started working consistently.Has anyone seen similar behavior or identified a root cause related to Akamai edge servers, DNS resolution, or geo-location routing?
host cp.icr.io
cp.icr.io is an alias for geo.icr.io.
geo.icr.io is an alias for geo.global.icr.io.akadns.net.
geo.global.icr.io.akadns.net is an alias for uk.icr.io.akadns.net.
uk.icr.io.akadns.net has address 158.176.193.128
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
