(InaccessibleImage) The image 'docker.io/presearch/node:latest' in container group '...' is not accessible. Please check the image and registry credential.

C Riley 0 Reputation points
2023-02-12T23:09:50.4266667+00:00

I have several containers in US regions (eastus, centralus, westus) all failing with the same error. The same containers are running fine in other regions in the world (brazilsouth, centralindia, francecentral, etc.). These just started failing last week and I'm unable to create/restart containers. These containers have been working without issue for >1 year until last week.

I've attempted using just --image presearch/node:latest and docker.io/presearch/node:latest but this doesn't help either.

Has something changed in azure cli such that we need to specify a new/different parameter?

CLI example

az container create --resource-group [redacted] --name [redacted] --image docker.io/presearch/node:latest --cpu 1 --memory 1 --dns-name-label [redacted] --environment-variables E1=V1 --azure-file-volume-share-name [redacted] --azure-file-volume-account-name [redacted] --azure-file-volume-account-key [redacted] --azure-file-volume-mount-path /app/node --location eastus

Error

(InaccessibleImage) The image 'docker.io/presearch/node:latest' in container group 'redacted' is not accessible. Please check the image and registry credential.

Code: InaccessibleImage

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
669 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Goncalo Correia 266 Reputation points Microsoft Employee
    2023-02-15T11:36:16.24+00:00

    Hi @C Riley

    Thanks for reaching Microsoft Q&A
    This issue is related to the lack of an image manifest, as you can check with the command:

    docker manifest inspect docker.io/presearch/node

    Azure ACI requires images to have a manifest and so that image although public, currently will not run in Azure ACI,
    Please note that Microsoft is aware of this and the product group is looking into this matter,

    As a workaround you can push that same image to an Azure ACR or other repository, that will add the required manifest and you will be able to run the container with the image.

    Hope this helps. Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

    2 people found this answer helpful.