containerinstance.ContainerGroupsClient#CreateOrUpdate Failure

Question

containerinstance.ContainerGroupsClient#CreateOrUpdate Failure

Sahaj Malla 1

containerinstance.ContainerGroupsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InaccessibleImage" Message="The image 'docker/aci-hostnames-sidecar:1.0' in container group 'django' is not accessible. Please check the image and registry credential."

SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee Moderator

2021-06-22T11:14:23.843+00:00

@Sahaj Malla , Are you logged into the private container registry from the Docker CLI while performing docker compose up?

You can deploy private images to ACI that are hosted by any container registry. You need to log into the relevant registry using docker login before running docker run or docker compose up. The Docker CLI will fetch your registry login for the deployed images and send the credentials along with the image deployment information to ACI. In the case of the Azure Container Registry, the command line will try to automatically log you into ACR from your Azure login. You don’t need to manually login to the ACR registry first, if your Azure login has access to the ACR. [Reference]

Is the image located on an Azure Container registry? If so, is Admin User enabled on the ACR? Does your Azure login have access to the ACR?
Floris Verhoeven 1 Reputation point

2021-06-22T11:29:31.997+00:00

I have a similar issue, public Docker containers are no longer found with the message: The image 'atmoz/sftp:latest' in container group 'partner-sftp-group' is not accessible. Please check the image and registry credential.

Not even the default getting-started container from Docker is available. The same image did work yesterday and also works when pulling directly in Docker.