Azure WebApp Fails to pull from ACR after making zero changes

Question

I deployed an Azure WebApp successfully pulling from Azure Container Registry yesterday. After the day, I stopped the WebApp. When I attempted to turn it back on, I received the following error message:

• 2023-04-16T17:05:45.988Z ERROR - Pulling docker image itinerary-creator-backend:latest failed:
  2023-04-16T17:05:46.067Z ERROR - DockerApiException: Docker API responded with status code=NotFound, response={"message":"pull access denied for itinerary-creator-backend, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"}
  2023-04-16T17:05:46.069Z WARN - Image pull failed. Defaulting to local copy if present.
  2023-04-16T17:05:46.073Z ERROR - Image pull failed: Verify docker image configuration and credentials (if using private repository) Can someone help me figure out what is going wrong? The following has been verified:

1. The System Assigned identity of the WebApp has the ACRPull role on the Azure Container Registry
2. The image and tag EXIST in the Azure Container Registry --> Repositories
3. The Deployment Center in the Azure Portal for the WebApp shows the following correctly
   1. System Assigned Identity
   2. Azure Container Registry name
   3. Image name
   4. Image tag
4. The APP_SETTINGS have all of the following set properly
   1. DOCKER_REGISTRY_SERVER_URL
   2. DOCKER_REGISTRY_SERVER_USERNAME
   3. DOCKER_REGISTRY_SERVER_PASSWORD

Answer 1

I have a similar issue. This kind of problem should be a must fix for any cloud provider. These problems are very random with web app deployment using container and I have to spend a full day trying to get it working only to have the same problem again next day for apparently no reason. Just restarting the app is not a solution - MSFT should get to the root of these problems.

Answer 2

Running into same problem.

All settings work great interactively...hit save...and it loses its mind...barfs and says it can load the container because of an authentication issue?

what exactly was it doing when it authenticated.

So many years...so many problems...azure web apps are just a terrible black box that can fail at any moment.

good luck this will always be a buggy service...10 years running.

i wish they would start over and dump their entire code base that was built just for .NET and not containers or any other code platform.

Answer 3

It seems like the error message is indicating that the WebApp is unable to pull the Docker image from the Azure Container Registry. Based on the information you have provided; it appears that the WebApp is properly configured to access the Azure Container Registry. However, there are a few things you can try to resolve the issue:

1. Check if the image and tag are still available in the Azure Container Registry. It is possible that the image and tag were deleted or overwritten, which could cause the WebApp to fail to pull the image.
2. Check if the Azure Container Registry is running and accessible. You can try to access the Azure Container Registry directly to verify that it is running and accessible.
3. Check if the Docker image configuration is correct. Verify that the Docker image configuration in the WebApp is correct, including the Docker registry server URL, username, and password.
4. Try restarting the WebApp. Sometimes, restarting the WebApp can resolve issues with pulling Docker images. If none of these steps resolve the issue, it is possible that there is an issue with the WebApp or Azure Container Registry that requires further investigation. Please reply to us and let us know if that is the case.