Issue in accessing image from Azure Container Registry...

Chandrakant Pawle 81 Reputation points
2024-05-24T11:51:57.97+00:00

Hello

I having issue in accessing ACR image while working on Azure Container Instances

Step 1: Created ACR service on Azure Portal

Step 1: Created ACR image using VS 2022 -> Publish

Step 2: Enabling admin user. Container Registry -> Settings \ Properties. Check on Admin User and Save

Step 3: Creating ACI

  • Image source = Azure Container Registry
  • Registry = cpregistry1

While creating ACI it gives following error

The image 'cpregistry1.azurecr.io/webapplication2:latest' in container group 'cp-container1' is not accessible. Please check the image and registry credential. (Code: InaccessibleImage)

Pls tell me what is reason here.... I guess, some configuration may be missing here

Regards

Chandrakant

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
415 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
662 questions
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,053 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anveshreddy Nimmala 3,285 Reputation points Microsoft Vendor
    2024-05-27T02:57:12.9766667+00:00

    Hello Chandrakant Pawle,

    Welcome to microsoft Q&A, thankyou posting your query here.

    Check if your image has tagged correctly .

    Check if the credentials used are correct for registry

    Check if your registry is private or public , if f the registry is private, make sure that the system identity of your online endpoint has the acrPull role for the registry. You can grant this role using the Azure portal.

    Private container registry is a registry that is only accessible to authorized users. Private registries are typically used by organizations to store and manage their own container images. Private registries provide more control over who can access the images and how they are used.

    Hope this helps you.

    0 comments No comments

  2. Andriy Bilous 11,011 Reputation points MVP
    2024-05-30T04:35:11.38+00:00

    Hello Chandrakant Pawle

    There could be multiple reasons having this kind of issue
    Maybe you're trying to use a service principal to access the Azure container registry.
    This scenario can occur because of one of the following reasons:

    • You specified incorrect credentials when you tried to create the container instance.
    • You specified the correct credentials, but the service calls on Container Instances are blocked by firewall rules in the Azure container registry.

    Solution:
    You must use a managed identity to allow the Container Instances trusted service to access the container registry. For more information, see Allow trusted services to securely access a network-restricted container registry. You can also learn more at Deploy to Azure Container Instances from Azure Container Registry using a managed identity.

    https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-instances/configuration-setup/inaccessible-image

    0 comments No comments