Title: InaccessibleImage Error - Unable to Pull Image from ACR in Azure Container Instance

Neetu Pal 40 Reputation points
2025-03-02T22:38:44+00:00

Issue Summary:

The Azure Container Instance (ACI) is unable to pull the image ***/todoapp/91 from the Azure Container Registry (ACR), resulting in an InaccessibleImage error. This issue is likely due to missing permissions, incorrect registry credentials, or an incorrect image path.

Steps to Reproduce:

Deploy a container instance using the following command:

az container create --resource-group <RESOURCE_GROUP> \

--name day10app \

--image <ACR_LOGIN_SERVER>/todoapp:91 \

--registry-login-server <ACR_LOGIN_SERVER> \

--registry-username <USERNAME> \

--registry-password <PASSWORD>

Check the container instance logs for errors.

Expected Results:

The container instance should successfully pull the image from the Azure Container Registry (ACR) and start running.

Actual Results:

The container deployment fails with the following error:

ERROR: (InaccessibleImage) The image '***/todoapp/91' in container group 'day10app' is not accessible. Please check the image and registry credential.

Code: InaccessibleImage

Message: The image '***/todoapp/91' in container group 'day10app' is not accessible. Please check the image and registry credential.

Error Details:

The image ***/todoapp/91 is not accessible in ACI.

Possible causes:

The image does not exist in ACR.

ACI does not have the AcrPull permission.

Incorrect ACR credentials used during deployment.

Team, does anyone know why ACI is unable to pull the image at this stage?

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
741 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vinodh247 29,361 Reputation points MVP
    2025-03-03T01:00:28.6866667+00:00

    Hi ,

    Thanks for reaching out to Microsoft Q&A.

    The InaccessibleImage error in ACI typically occurs due to issues such as the image not existing in ACR, missing AcrPull permissions, incorrect registry credentials, or an improperly formatted image path. To resolve this, verify that the image exists in ACR, ensure ACI has the necessary AcrPull role assignment if using a managed identity, and confirm that the correct registry username and password are being used. Additionally, if ACR is private, ACI must have network access to it. Checking these factors and making the necessary adjustments should resolve the issue.

    Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.