Hi,
It sounds like a frustrating issue! Here are a few steps you can try to resolve this:
Restart the WebApp: Sometimes, a simple restart can force the web app to pull the latest image. You can do this from the Azure portal or using the Azure CLI:
az webapp restart --name <YourAppName> --resource-group <YourResourceGroup>
Clear Cached Data: Ensure that any cached data is cleared. In the Azure portal, go to your web app’s settings and enable the option to remove additional files at the destination under the "File Publish Options".
Check Deployment Logs: Verify the deployment logs in the Azure portal to ensure that the new image is being pulled and there are no errors during the process.
Verify Image Tag: Make sure that the image tag in your web app configuration matches the tag of the newly pushed image. Sometimes, using the latest
tag can cause issues if the web app doesn’t detect the change.
Configure Webhooks: Set up a webhook in your container registry to trigger a redeployment whenever a new image is pushed. This can help automate the process and ensure the latest image is always used.
Check Connectivity and Credentials: Ensure that your web app can connect to the container registry and that the credentials are correct. Incorrect credentials can prevent the web app from pulling the latest image.
If these steps don’t resolve the issue, please let me know, and we can dive deeper into the problem.