Azure Container Registry Reviews

The solution is really useful because whenever you want to deploy the containers, you need to have a place to store those container codes so that they can deploy easily. It is always better to store those codes in the solution itself so that you can deploy them through the pipelines. That is where Azure Container Registry comes into the picture. And also, it can duplicate to different zones and locations.

The most valuable feature is the zone replication and resiliency, because otherwise you have to build a system, and you need to worry about the resiliency and the backup of those codes. With this solution, you don't have to worry about all those things.

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.

I have been using the solution for three years.

The solution has built-in resiliency and replication zone availability so it is very stable.

The solution is scalable depending on the tier you select.

The initial setup is very straightforward with no hassle at all. The deployment takes about one hour.

The fees depend on the storage you are using. Azure Container Registry, has no cost, but you pay for storage service. So you pay based on the amount you store.

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 currently deploy the application to facilitate CI/CD processes. I'm in the process of identifying and setting it up.

The continuity screen is a valuable feature. What I initially attempted was deploying an application directly into the company's infrastructure, specifically using the agent mobility infrastructure. However, I've now shifted my approach to utilizing a deposit fee. This change will enable me to conduct operational CI/CD testing.

I haven't delved deep into the details, and I cannot add anything as of now, but they can improve their scalability.

I have been working with Azure Container Registry for some time. 

It is stable. I would rate it an eight out of ten. 

It is scalable. I would rate it an eight out of ten. 

We used Azure Container Registry because I discussed it with AWS, and while it's developer-friendly, in my research, I've noticed that Azure seems to be the more prominent solution in the market. This preference is due to its cost-effectiveness and the familiarity many have with the platform.

The initial setup was straightforward. The deployment took one day.

I would rate the pricing a four out of ten.

I would rate it a nine out of ten.

Our company uses the solution to store docker or other types of images for products and software that we are developing. We use the solution for its intended purpose and how most other companies use it.

We have some pipelines in Azure DevOps and we store images created through the pipelines in our registry. We use the registry for deployments. 

We work for a contractor who has thousands of projects. It is difficult to determine how many people use the solution because of the number of projects. It seems to be the trend with their projects to use the solution along with AK and Kubernetes clusters. Our specific team includes 15 people who use the solution quite often. 

Specific tokens can be used to set folder structure or restrict things like read or write access. 

The solution has good accessibility and is quite easy to understand. 

Configurations are quite simple. 

The solution could always improve its security measures with regard to access. 

I have been using the solution for four years. 

The solution is stable with no issues so stability is rated a ten out of ten. 

The solution is scalable so scalability is rated a nine out of ten. 

I have not needed technical support. 

I have not used other solutions. 

The setup was quite easy and not complicated at all. Other setups, changes, or implementations of the token skew are quite simple as well.  

We have the automation to set up the ACR via the Terraform and also have a graphic user interface that makes it quite easy to create. 

The setup is rated a nine out of ten. 

We implemented the solution in-house and deployment was quite fast because we had Terraform. From the output we saw, deployment was very fast compared to some other resources in Azure Cloud. 

The Premium version that we use includes some enhancements but is still quite okay with regard to pricing. The solution is worth the money. 

From time to time, we check pricing for our resources to see if there is anything we can do to reduce costs. For the solution, the price is quite low so we don't need to worry about it. 

The solution is the best fit for us because we use Azure Cloud which is the native resource for containers.

I recommend that you definitely use the solution. I don't have any issues with it and configurations are quite simple. The scalability is quite good. The solution provides everything that is needed.

I rate the solution a nine out of ten. 

We use the solution for image processing. We store and manage images. You can utilize the tools to recognize and organize images. For example, you have an image and gather two more images, each with different versions and tagging system. You should filter different variations of these images. Based on the algorithm, you can generate multiple images and then deploy them using Docker for testing or in AKS. We should know how to create and tag the image as part of microservices.

You can access the Azure Container Registry and store container images. You can also see the versioning history and other details about your images.

The solution could provide more integration.

I have been using Azure Container Registry for three years.

The GUI and interface are good, and we can navigate easily, but it has the typical Azure interface.

I rate the solution’s stability an eight out of ten.

You can buy a license and set up another Azure Container Registry when you want to have a more image repository.

We deploy to AKS as a service. Once deployed, people generally access Kubernetes indirectly through ACR. People don't directly access ACR. There is no problem with multiple users accessing ACR.

We have 1000 users using this solution.

The initial setup is straightforward. You should create an ACR and then configure communication between ACR and ACS.

Deployment takes a maximum of five minutes to push to ACR. Once the docker build is running and the Docker file is fine. Then, you must go to the login page here and put the image.

We have a one-year or two-year contract. We can extend it to a ten-year contract because it is a stable application. We have our images ready, with which we want to focus on the customer. We are using and maintaining them. ACR even supports some kind of complex work.

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.

We use Azure Container Registry to store our container images and the solution that we build for automation.

Azure Container Registry is an easy-to-install, easy-to-configure, and easy-to-deploy solution. The solution requires minimal overhead. To manage our own Azure Container Registry, we go to Azure, create a registry for us, and start publishing the images.

The way Azure RBAC is configured, our oldest access control, allows us to leverage that so that no one can push it, and we can use it in our solution. I used Azure Container Registry with my Azure Batch job to run the tagging solution.

I have been using Azure Container Registry for six months.

I rate Azure Container Registry ten out of ten for stability.

It is good enough to store all the images we need, and we can create as many container registries as we need.

I rate Azure Container Registry ten out of ten for scalability.

The solution's initial setup is easy. On a scale from one to ten, where one is easy and ten is difficult, I rate the solution a one out of ten for the ease of its initial setup.

You need to know how containers and docker images work when interacting with and installing Azure Container Registry.

Azure Container Registry can be deployed within two to three minutes.

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.

Our primary use case for the solution is storing Docker images on Azure Container Registry, and we deploy it on cloud.

The solution has helped minimize time by ensuring there is no vulnerability. If there is any vulnerability in the Docker image, the build fails and does not allow it to deploy to a production environment.

The scanning of Docker images is the most valuable feature.

It's not an open source, and we pay per hour to Microsoft Azure.

We have been using the solution for six months.

The solution is stable. I rate it as eight out of ten.

The solution is scalable, and ten users currently utilize it in our organization. I rate the scalability as eight out of ten.

The initial setup is straightforward, and you have to take the service directly from Microsoft Azure Service from Azure Portal. A third party completed the deployment.

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.

It's a container repository. It's like a Docker hub. With it, you can post the image of the container right there.

We can use these images in an ECR on Kubernetes, which has been quite useful to the organization. 

It's great for storing images on containers.

The solution has no areas that need improvement. 

I've been using the solution for five years. I've used the product for a while at this point. It's been many years. 

I'd rate the stability zero out of ten. 

I'd rate the scalability zero out of ten.

Technical support has been very helpful and responsive. 

Positive

We have witnessed an ROI while using the solution. 

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 mainly use Container Registry to containerize applications and ship/deploy them.

The most valuable feature is that it's easy to download, install and manage.

The security, dashboards, and monitoring system could be improved.

I've been using this solution for two years.

I've had no issues with stability.

The initial setup was easy.

We used an in-house team to implement.

Container Registry is reasonably priced.

I would rate Container Registry seven out of ten.