You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am encountering an issue with Azure Container Registry where it is not reflecting the latest changes in my code. I am running in Azure AKS.
To Reproduce
Steps to reproduce the behavior:
I made changes to my code, built the image, and pushed it to the registry with the tag test:v1.
I then deleted the test:v1 image from the registry.
After making additional modifications to the code, I rebuilt the image and pushed it again to the registry with the same tag test:v1.
However, the registry does not seem to recognize the latest updates. It continues to display the output from the old version of the code associated with the test:v1 tag.
I am facing the issue while deploying the application in AKS.
Expected behavior
The expected behavior when you push an updated image to Azure Container Registry with the same tag as a previously deleted image is that the registry should store and serve the new image. When you pull the image by its tag (e.g., test:v1), you should receive the latest version that was pushed under that tag.
Any relevant environment information
OS: [Linux]
The text was updated successfully, but these errors were encountered:
Describe the bug
I am encountering an issue with Azure Container Registry where it is not reflecting the latest changes in my code. I am running in Azure AKS.
To Reproduce
Steps to reproduce the behavior:
However, the registry does not seem to recognize the latest updates. It continues to display the output from the old version of the code associated with the test:v1 tag.
I am facing the issue while deploying the application in AKS.
Expected behavior
The expected behavior when you push an updated image to Azure Container Registry with the same tag as a previously deleted image is that the registry should store and serve the new image. When you pull the image by its tag (e.g., test:v1), you should receive the latest version that was pushed under that tag.
Any relevant environment information
The text was updated successfully, but these errors were encountered: