You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the command az acr login -n shazdevops to login
Could not connect to the registry login server 'shazdevops.azurecr.io'. Please verify that the registry exists and the URL 'https://shazdevops.azurecr.io/v2/' is reachable from your environment.
Try running 'az acr check-health -n shazdevops --yes' to diagnose this issue.
The error happens after a long delay around 2 minutes
2. Run the command az acr check-health -n shazdevops --yes throws the following output
Docker daemon status: available
Docker version: 'Docker version 26.1.3, build 8e96db1c32, platform linux/amd64'
Docker pull of 'mcr.microsoft.com/mcr/hello-world:latest' : OK
Azure CLI version: 2.60.0
DNS lookup to shazdevops.azurecr.io at IP 20.62.128.0 : OK
2024-05-20 12:10:31.757626 An error occurred: CONNECTIVITY_CHALLENGE_ERROR
Registry 'shazdevops.azurecr.io' did not issue a challenge.
Please refer to https://aka.ms/acr/errors#connectivity_challenge_error for more information.
Expected behavior
The login must succeed with "Login Succeeded" message
Screenshots
CLI
Azure Portal
Any relevant environment information
OS: Ubuntu Linux, Arch Linux
Azure CLI: 2.60.0
Docker version: 'Docker version 26.1.3, build 8e96db1c32, platform linux/amd64'
Datetime (UTC) when the issue occurred: Noticing at 11:52 am UTC, Monday 20th May 2024
Describe the bug
Unable to login to our azure container registry, shazdevops.azurecr.io, via the azure cli. Using the azure cli version 2.60 on Linux
To Reproduce
Steps to reproduce the behavior:
az acr login -n shazdevops
to loginThe error happens after a long delay around 2 minutes
2. Run the command
az acr check-health -n shazdevops --yes
throws the following outputExpected behavior
The login must succeed with "Login Succeeded" message
Screenshots
CLI
Azure Portal
Any relevant environment information
Additional context
If any information is a concern to post here, you can create a support ticket or send an email to [email protected].
The text was updated successfully, but these errors were encountered: