Not able to pull docker image from Container Registry

Moresi, Marco 21 Reputation points
2021-09-16T13:27:22.91+00:00

Hello community,
I'm facing a problem, my ACR in my resource group was deleted and I couldn't create any instance. I created again and now I can create instances but i'm having problems to run the dataset profile. It's failing to pull the image docker.

This is the output

AzureMLCompute job failed.  
FailedPullingImage: Unable to pull docker image  
	imageName: 19acd0cdf57549bcace363c924cf045b.azurecr.io/azureml/azureml_e7e3dfebc6129c75c60868383ebc992f  
	error: Run docker command to pull public image failed with error: Error response from daemon: Get https://19acd0cdf57549bcace363c924cf045b.azurecr.io/v2/azureml/azureml_e7e3dfebc6129c75c60868383ebc992f/manifests/latest: unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information.  
.  
	Reason: Error response from daemon: Get https://19acd0cdf57549bcace363c924cf045b.azurecr.io/v2/azureml/azureml_e7e3dfebc6129c75c60868383ebc992f/manifests/latest: unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information.  
  
	Info: Failed to setup runtime for job execution: Job environment preparation failed on 10.0.0.5 with err exit status 1.  

The ML Studio has the following permissions on the ACR permissions

132698-unbenannt.png

The docker image appears in the repositories of the ACR

132781-unbenannt2.png

Any hint how can i solve this problem?

Thanks in advance

Azure Machine Learning
Azure Machine Learning
An Azure machine learning service for building and deploying models.
2,663 questions
0 comments No comments
{count} votes

Accepted answer
  1. romungi-MSFT 43,366 Reputation points Microsoft Employee
    2021-09-16T14:37:51.767+00:00

    @Moresi, Marco Does this container registry have the admin account enabled? A requirement while creating a workspace with an existing container registry is to have the admin account enabled.

    If you have already enabled it then a re-sync of keys might be required for your workspace.

    az ml workspace sync-keys -w <workspace-name> -g <resource-group-name>  
    

    Deleting the default container registry used by the workspace can also cause the workspace to break.

    3 people found this answer helpful.

0 additional answers

Sort by: Most helpful