Azure Container Registry OverviewUNIXBusinessApplication

Azure Container Registry is the #1 ranked solution in top Container Registry tools. PeerSpot users give Azure Container Registry an average rating of 8.0 out of 10. Azure Container Registry is most commonly compared to Amazon ECR: Azure Container Registry vs Amazon ECR. Azure Container Registry is popular among the large enterprise segment, accounting for 70% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 16% of all views.
What is Azure Container Registry?

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.

Azure Container Registry was previously known as Microsoft Azure Container Registry.

Azure Container Registry Customers

DNV GL, Alaska Airlines, Finastra

Azure Container Registry Video

Azure Container Registry Pricing Advice

What users are saying about Azure Container Registry pricing:
  • "Azure is a bit expensive."
  • "Azure Container Registry, has no cost, but you pay for storage service."
  • Azure Container Registry Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    DevOps Consultant at GP Coders
    Consultant
    Top 10Leaderboard
    Easy to use, private, secure, and it performs well
    Pros and Cons
    • "One of the benefits of this solution is that it's private and secure."
    • "The deployment is an area that needs improvement, as it can take some time to deploy."

    What is our primary use case?

    I am a DevOps consultant. I provide the architecture, assessments, and optimization of the services that we use to build a better infrastructure, and other services.

    We are basically using Azure Container Registry for a project that we have in the healthcare domain. There, we use the container registry and as well as Azure DevOps, apart from the Azure Cloud and the built release pipeline, along with this container registry and the self-hosted server. 

    I would say that this allows us to build, store, and manage the container images and the artifact in the private registry that Azure provides. 

    It's a managed container registry that we don't need to configure or set up within our premises. It's all in the cloud. The login and the portal id where we can store that information, and the containers. 

    We can also see a list of images located in the repository. For example, I can pull any Docker image using the Docker command. I can then store that image within the repository, within this Docker Registry Container.

    I don't have to go to the Docker Hub or any other hub. This is one of the safest private repositories over the cloud that I have, that I can use.

    This is one of the most beneficial solutions to be used over the cloud.

    What is most valuable?

    One of the benefits of this solution is that it's private and secure. It's easy to use, it's fast, and it's scalable. 

    We can have that OCA format that we can use and it's a multi-tenant service, which we use for the endpoint data that we have. 

    We can automate container builds for testing and other purposes, and we can use the CLI (command-line interface) to interact with the registry. 

    We can manage Windows and Linux containers within a single registry. We don't have to create multiple container registries, different images, and containers. 

    These are the benefits of having the Container Registry and we can use the Webhook as well, for security purposes and for pushing the container image using the CI/CD pipeline. 

    These are the benefits we get using the Container Registry.

    This solution has multiple features and I can't really say that I can rely on, or that there is only one feature or one that I love more. 

    The app services and the DC/OS and the KS, also the service tiers that they are providing, security using the logins, images, artifacts, and many more.

    The task of pushing and deploying images that we use in the containers is very good.

    It's very secure and it uses authentication.

    Security, the deployment pipelines, and the developers are using the ACR task instead of using other third-party products.

    What needs improvement?

    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.

    What do I think about the stability of the solution?

    It's very stable because it has security integration as well.

    It's integrated with the echo security, which helps the developmental production life cycle controls, in the container application that we use.

    It's very efficient and stable to use.

    What do I think about the scalability of the solution?

    This solution is scalable.

    I'm not using it that extensively. I have a 40/50GB of data that I am storing using the container images. That hasn't cost me very much, I am using it in a very optimal way.

    How are customer service and support?

    I have not contacted technical support. We haven't needed it yet.

    Which solution did I use previously and why did I switch?

    Previously, I used open-source only. 

    I never used the AWS (Amazon Web Services) providing the ECR, the elastic container Registry. It's a bit expensive compared to Azure. I am certified, but I haven't used that.

    Cons of an open-source product are that it has limited security features, that I am looking for without replication. It doesn't have the access key features and the policies which are positive with ACR.

    How was the initial setup?

    The initial setup is straightforward for me. It was not complex.

    I didn't find it to be difficult in setting up the ACR with the Docker containers that we were using.

    It took time to deploy this containerization and the application. For example, when creating the ACR and you click to deploy it and create the replication, it takes some time to create the replication.

    I feel that It took more than thirty minutes to complete the deployment.

    My initial strategy was to secure the images that we use for the microservices and the web services for production. I didn't want to include any other repository. I just wanted to have a secure ability instead of creating my own or using the open-source repository.

    That was my initial purpose because it provides the access key and the web host, which other third-party open-sourced solutions are not providing. This allows us to use the active directory to access the services.

    The solution doesn't require any further maintenance post-deployment.

    What was our ROI?

    It gives me exposure and learning in this technology. Apart from that, it's the client who is paying me to manage and service the infrastructure. 

    What's my experience with pricing, setup cost, and licensing?

    Azure is a bit expensive.

    What other advice do I have?

    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.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Director - Cloud Security at a financial services firm with 10,001+ employees
    Real User
    Top 20Leaderboard
    Zone replication and resiliency are built in, but the technical service staff requires more knowledge
    Pros and Cons
    • "The solution has built-in resiliency and replication zone availability so it is very stable."
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using the solution for three years.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    The solution is scalable depending on the tier you select.

    How was the initial setup?

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

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    PeerSpot user
    Engineering Manager at a healthcare company with 1,001-5,000 employees
    Real User
    Top 20Leaderboard
    Easy to download, install and manage but dashboards and monitoring system could be improved

    What is our primary use case?

    I mainly use Container Registry to containerize applications and ship/deploy them.

    What is most valuable?

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

    What needs improvement?

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

    For how long have I used the solution?

    I've been using this solution for two years.

    What do I think about the stability of the solution?

    I've had no issues with stability.

    How was the initial setup?

    The initial setup was easy.

    What about the implementation team?

    We used an in-house team to implement.

    What's my experience with pricing, setup cost, and licensing?

    Container Registry is reasonably priced.

    What other advice do I have?

    I would rate Container Registry seven out of ten.

    Which deployment model are you using for this solution?

    Private Cloud
    Disclosure: My company has a business relationship with this vendor other than being a customer: partner
    Flag as inappropriate
    PeerSpot user