From time to time, I've noticed some hiccups in Azure Container Registry. For example, the solution didn't work thrice, and the only solution Microsoft provided was to update Azure Container Registry. I've noticed that the IP address attached to the machine changed in the end. The solution doesn't always work perfectly, so from time to time, you cannot pull or push the Docker images to the environment, which is an area for improvement. The only solution to this issue is to establish one more Azure Container Registry and attach the new IP address and DNS name to it. The accessibility of Azure Container Registry also has room for improvement because the solution is not always accessible 24 x 7. I experienced this three times when the service wasn't responding, so I could not push or pull images, and I had to decommission Azure Container Registry and redeploy it. The only good thing is that I already have the infrastructure as a code, which makes it easier for me to set the solution up and create the environment from scratch. Still, the process will be annoying for people with manual operations around Azure Container Registry, mainly because the issue happens from time to time. The only functionality I want to add to the service is the auto-scanning of images, which should tell me if there's any issue with the Docker images I need to address. The JFrog Artifactory has this functionality, but it would be an excellent feature to add to Azure Container Registry to scan the Docker images and check for possible vulnerabilities.
Cloud Infrastructure Consultant at a tech services company with 201-500 employees
MSP
Top 10
2022-12-23T14:24:18Z
Dec 23, 2022
I don't have many issues with the solution but I would like it if the access keys could be stored in a master key vault. If they could be hashed and the value of that hash stored in the key vault so that it's not visible on the portal, would be a helpful addition.
Director - Cloud Security at a financial services firm with 10,001+ employees
Real User
Top 10
2022-11-08T12:13:25Z
Nov 8, 2022
The solution has become more popular in the last few years but I find that the technical support has not increased their knowledge base, so more knowledgeable support staff can help improve the solution.
It's difficult to find areas of improvement. I have always found it to be better than any CI/CD pipeline. The deployment is an area that needs improvement, as it can take some time to deploy.
New Technologies Adoption Director at a tech services company with 11-50 employees
Real User
2020-11-11T04:55:56Z
Nov 11, 2020
It should be easier to use. It can have more graphical interfaces to manage containers. At present, the handling or management of the containers is very basic.
Sr. SDET at a tech services company with 201-500 employees
Real User
2020-11-06T22:17:00Z
Nov 6, 2020
Implementation needs improvement. We have a lot of open, online sources. Doing a deployment is easy for us. The only issue is when we have VPN connections and we try to pull the images from Container images to the local Dockers, it slows down. The images are slow when we have a VPN setup.
Azure Container Registry allows you to build, store, and manage container images and artifacts in a private registry for all types of container deployments. Use Azure container registries with your existing container development and deployment pipelines. Use Azure Container Registry Tasks to build container images in Azure on-demand, or automate builds triggered by source code updates, updates to a container's base image, or timers.
The solution could provide more integration.
I haven't delved deep into the details, and I cannot add anything as of now, but they can improve their scalability.
I suppose a more detailed management interface that's not available in Azure, if made available, would be useful.
We have found that it is sometimes difficult to pull images from the host application.
It's not an open source, and we pay per hour to Microsoft Azure.
From time to time, I've noticed some hiccups in Azure Container Registry. For example, the solution didn't work thrice, and the only solution Microsoft provided was to update Azure Container Registry. I've noticed that the IP address attached to the machine changed in the end. The solution doesn't always work perfectly, so from time to time, you cannot pull or push the Docker images to the environment, which is an area for improvement. The only solution to this issue is to establish one more Azure Container Registry and attach the new IP address and DNS name to it. The accessibility of Azure Container Registry also has room for improvement because the solution is not always accessible 24 x 7. I experienced this three times when the service wasn't responding, so I could not push or pull images, and I had to decommission Azure Container Registry and redeploy it. The only good thing is that I already have the infrastructure as a code, which makes it easier for me to set the solution up and create the environment from scratch. Still, the process will be annoying for people with manual operations around Azure Container Registry, mainly because the issue happens from time to time. The only functionality I want to add to the service is the auto-scanning of images, which should tell me if there's any issue with the Docker images I need to address. The JFrog Artifactory has this functionality, but it would be an excellent feature to add to Azure Container Registry to scan the Docker images and check for possible vulnerabilities.
The solution has no areas that need improvement.
I don't have many issues with the solution but I would like it if the access keys could be stored in a master key vault. If they could be hashed and the value of that hash stored in the key vault so that it's not visible on the portal, would be a helpful addition.
The solution has become more popular in the last few years but I find that the technical support has not increased their knowledge base, so more knowledgeable support staff can help improve the solution.
The security, dashboards, and monitoring system could be improved.
It's difficult to find areas of improvement. I have always found it to be better than any CI/CD pipeline. The deployment is an area that needs improvement, as it can take some time to deploy.
It should be easier to use. It can have more graphical interfaces to manage containers. At present, the handling or management of the containers is very basic.
Implementation needs improvement. We have a lot of open, online sources. Doing a deployment is easy for us. The only issue is when we have VPN connections and we try to pull the images from Container images to the local Dockers, it slows down. The images are slow when we have a VPN setup.