Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides guidance on how to troubleshoot issues with Azure Container Registry on Azure Stack Hub.
Enable diagnostic collection settings
Platform metrics and the activity log are collected and stored automatically but can be routed to other locations by using a diagnostic setting.
Resource Logs are not collected and stored until you create a diagnostic setting and route them to one or more locations.
See Create diagnostic setting to collect platform logs and metrics in Azure for information about creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect. The categories for Azure Container Registry are listed in Azure Container Registry monitoring data reference.
On Azure Stack Hub, the only destinations for these logs and metrics are either a local Azure Storage account on Azure Stack Hub or an Event Hubs instance on Azure Stack Hub. Log analytics workspaces are not available locally on Azure Stack Hub. For more information about the format of logs when using an Azure Storage account, see Azure resource logs.
Detect common issues
You might occasionally encounter problems when using Azure Container Registry on Azure Stack Hub. For example, you might not be able to pull a container image because of an issue with Docker in your local environment. Or, a network issue might prevent you from connecting to the registry.
As a first diagnostic step, run the az acr check-health command to get information about the health of the environment and optionally access to a target registry. This command is supported in Azure CLI version 2.28.0 or later. If you need to install or upgrade CLI, see Install Azure CLI.
For more information about running this command, see Check registry health.
Troubleshoot specific issues
To troubleshoot login issues, see Troubleshoot login to registry.
To troubleshoot potential network issues, see Troubleshoot network issues with registry.
To troubleshoot quota-related issues, there are three cases in which you might encounter quota-related issues with Azure Container Registry on Azure Stack Hub:
- When the number of container registries has exceeded the quota set by your Azure Stack Hub operator.
- When the size of one (or more) of your container registries exceeds the quota set by your Azure Stack Hub operator*.
- When the storage capacity of your Azure Stack Hub stamp is exceeded.
*By default, the maximum size of a container registry is 100 GiB, but your operator might have changed this based on their needs.
In any of these three cases, you receive an error saying that a quota was exceeded, or an error saying that some operation is disallowed. To resolve the error, contact your Azure Stack Hub operator, who can increase quotas and/or reconfigure stamps. For more information about how operators manage capacity and quotas for Azure Container Registry on Azure Stack Hub, see Manage container registry quotas.
Find your registry Resource ID for support
You might need to use the resource ID for your container registry to help resolve issues. You might need to provide this ID to your cloud operator or to Azure support. Follow these steps to get your resource ID:
Open the Azure Stack Hub user portal.
Navigate to your container registry.
Select JSON view.
Find the resource ID. Select Copy.
