If everything is hosted in Azure, it's recommended to go with Azure Container Registry instead of Docker Hub. It is definitely useful. I'd rate the solution nine out of ten.
We use GitHub for our repository. For our CI/CD flow, we publish our container images to ACR using the available GitHub Actions. For the CI process, we publish the images, and for deployment, we use AKS. Once the images are pushed to ACR, they are pulled into our AKS clusters, completing the deployment. If your infrastructure is hosted on Azure, it's one of the best online solutions. I've utilized peer support and documentation, and in terms of cost benefits, resiliency, high availability, and security features, it remains one of the top options. I recommend it to anyone deploying Docker files and containers. Overall, I rate the solution an eight out of ten.
Strategic Head | Azure Services and GRC at Braintree
Real User
Top 5
2024-07-01T12:15:00Z
Jul 1, 2024
The horizontal scaling and auto-scaling capabilities are excellent. If our container starts taking on more load, we can load balance the container images into new instances and scale back down when the load decreases. I would definitely recommend it. Overall, I would rate it an eight out of ten.
I would recommend Azure Container Registry to other users because it has good security features. Overall, I rate Azure Container Registry a nine out of ten.
For this application, we have a team of technical people who are very available and are working on the application. We have two technical engineers. We currently don't have multiple capabilities, but we have already trained the team on ACR and Docker and are training some of them on AKS. They are now building applications. Overall, I rate the solution a seven out of ten.
I rate the solution as eight out of ten. Regarding advice, if you create an account in Azure Portal, there is a $200 free credit for the new user, and they can use this $200 free credit and practice an ACRA case later.
My team has eleven members, all using Azure Container Registry. The institution I belong to has other users of Azure Container Registry. Still, it's hard to say how many because of the policy that every application should have its Azure Container Registry for security purposes. My advice to any first-time user of Azure Container Registry or those looking to implement it is to build it as part of the infrastructure pipeline. When there is an issue with the service, it would be wise to auto-deploy it straight away instead of tweaking it from scratch because when you create Azure Container Registry from scratch, particularly when you set it up as not accessible to the public, every time you recreate it, you have to establish a dedicated connection and also set it up and keep the login password in the key vault, so there's some element of doing it manually, which is time-consuming. When there's some stability in Azure Container Registry, it's easier because you can trigger the pipeline, and it does everything you need after a few minutes versus spending one or two more days to set it up from scratch. I'd rate Azure Container Registry as eight out of ten because it has many features required in a container registry, and the only missing part is image scanning for vulnerabilities. The service even allows you to disable public access, which is quite good because that's not always out of the box for other cloud providers. You already have the Webhooks in Azure Container Registry, which I'm trying to use. When there's a push or pull of information, you can inform other people or teams that there's a trigger, which is an excellent feature. Personally, the accessibility issue of Azure Container Registry, where the IP address is disabled, and you'd have to decommission and set the service up again, which affects stability, made me rate the service an eight rather than give it a perfect score. My institution has a partnership with Azure Container Registry.
I give the solution a seven out of ten. We have at least two clients that use this solution. There are a lot of ways to store your codes. You can obviously use your deployment tool, or the code repository to store the code like your GitHub or Azure DevOps. But when it comes to the Container Registry, it is better to store your container codes in Azure Container Registry itself, because it has a lot of advantages over a normal Git repository.
Overall, this solution is very beneficial. If my infrastructure or our services are within the Azure Cloud, and if I'm using the ECR, it's very helpful to maintain the images that we use for the web services or the microservices for the ATS and the dockers. We don't have to maintain those images for other third parties or other repositories. It's very good and for those who don't use it, you must look into it, and just go for it. I would rate this solution a ten out of ten.
New Technologies Adoption Director at a tech services company with 11-50 employees
Real User
2020-11-11T04:55:56Z
Nov 11, 2020
I would advise taking the time to go through the documentation before starting to use this solution. It is important to gain knowledge before you start using it. I would rate Azure Container Registry an eight out of ten.
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.
If everything is hosted in Azure, it's recommended to go with Azure Container Registry instead of Docker Hub. It is definitely useful. I'd rate the solution nine out of ten.
We use GitHub for our repository. For our CI/CD flow, we publish our container images to ACR using the available GitHub Actions. For the CI process, we publish the images, and for deployment, we use AKS. Once the images are pushed to ACR, they are pulled into our AKS clusters, completing the deployment. If your infrastructure is hosted on Azure, it's one of the best online solutions. I've utilized peer support and documentation, and in terms of cost benefits, resiliency, high availability, and security features, it remains one of the top options. I recommend it to anyone deploying Docker files and containers. Overall, I rate the solution an eight out of ten.
The horizontal scaling and auto-scaling capabilities are excellent. If our container starts taking on more load, we can load balance the container images into new instances and scale back down when the load decreases. I would definitely recommend it. Overall, I would rate it an eight out of ten.
I would recommend Azure Container Registry to other users because it has good security features. Overall, I rate Azure Container Registry a nine out of ten.
For this application, we have a team of technical people who are very available and are working on the application. We have two technical engineers. We currently don't have multiple capabilities, but we have already trained the team on ACR and Docker and are training some of them on AKS. They are now building applications. Overall, I rate the solution a seven out of ten.
I would rate it a nine out of ten.
My suggestion to others regarding the solution is that they need to read the documentation. I rate the overall product a nine out of ten.
We would rate this solution a nine out of ten.
I rate the solution as eight out of ten. Regarding advice, if you create an account in Azure Portal, there is a $200 free credit for the new user, and they can use this $200 free credit and practice an ACRA case later.
My team has eleven members, all using Azure Container Registry. The institution I belong to has other users of Azure Container Registry. Still, it's hard to say how many because of the policy that every application should have its Azure Container Registry for security purposes. My advice to any first-time user of Azure Container Registry or those looking to implement it is to build it as part of the infrastructure pipeline. When there is an issue with the service, it would be wise to auto-deploy it straight away instead of tweaking it from scratch because when you create Azure Container Registry from scratch, particularly when you set it up as not accessible to the public, every time you recreate it, you have to establish a dedicated connection and also set it up and keep the login password in the key vault, so there's some element of doing it manually, which is time-consuming. When there's some stability in Azure Container Registry, it's easier because you can trigger the pipeline, and it does everything you need after a few minutes versus spending one or two more days to set it up from scratch. I'd rate Azure Container Registry as eight out of ten because it has many features required in a container registry, and the only missing part is image scanning for vulnerabilities. The service even allows you to disable public access, which is quite good because that's not always out of the box for other cloud providers. You already have the Webhooks in Azure Container Registry, which I'm trying to use. When there's a push or pull of information, you can inform other people or teams that there's a trigger, which is an excellent feature. Personally, the accessibility issue of Azure Container Registry, where the IP address is disabled, and you'd have to decommission and set the service up again, which affects stability, made me rate the service an eight rather than give it a perfect score. My institution has a partnership with Azure Container Registry.
There isn't a specific version associated with the product. I'd advise potential users to just give it a try. I'd rate the solution five out of ten.
I rate this solution nine out of 10.
I give the solution a seven out of ten. We have at least two clients that use this solution. There are a lot of ways to store your codes. You can obviously use your deployment tool, or the code repository to store the code like your GitHub or Azure DevOps. But when it comes to the Container Registry, it is better to store your container codes in Azure Container Registry itself, because it has a lot of advantages over a normal Git repository.
I would rate Container Registry seven out of ten.
Overall, this solution is very beneficial. If my infrastructure or our services are within the Azure Cloud, and if I'm using the ECR, it's very helpful to maintain the images that we use for the web services or the microservices for the ATS and the dockers. We don't have to maintain those images for other third parties or other repositories. It's very good and for those who don't use it, you must look into it, and just go for it. I would rate this solution a ten out of ten.
I would advise taking the time to go through the documentation before starting to use this solution. It is important to gain knowledge before you start using it. I would rate Azure Container Registry an eight out of ten.
I would rate Azure Container Registry an eight out of ten. The setup should be simplified.