"The solution has built-in resiliency and replication zone availability so it is very stable."
"The continuity screen is a valuable feature."
"Provides secure duplication and the option for service webhooks."
"The solution allows you to isolate standard containers, which is its most valuable feature. Azure Container Registry does what it's supposed to do and gives you visibility into the Docker images, the logs, information on pulling and pushing the data, etc."
"Pricing is reasonable."
"We like the fact that this is a secure solution, that employs a token-based system, which can be used to manage all the applications under this product."
"Feature-wise, the security model and access controls are pretty straightforward and valuable"
"It's great for storing images on containers."
"It supports multi-cloud deployments across AWS, Azure, and GCP."
"We use the solution to compile the codes before publishing them. We utilize third-party containers and codes, downloading them to the JFrog Container Registry. Developers then access it from the JFrog Container Registry, and there's a specific job responsible for running and validating all security checks, ensuring compatibility. If there are any issues or if packages require updates, we manage those updates through this system."
"We have found that it is sometimes difficult to pull images from the host application."
"Lacks the option of having access keys stored in a master key vault."
"The setup process is mildly complex. There is no straightforward management platform, so there's a level of complexity to it."
"They can improve their scalability."
"The security, dashboards, and monitoring system could be improved."
"The deployment is an area that needs improvement, as it can take some time to deploy."
"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 setup for Azure Container Registry was a bit complex. Still, the main problem was that whenever a new image was generated, that new Docker image needed to be updated in Azure Container Registry."
"One challenge we face is related to performance. Our integration involves GitHab and JFrog Container Registry, with pipelines fetching data from GitHub and JFrog Container Registry for third-party code. However, there are instances where this process can slow down the pipeline."
"In my experience, there was a bit of a learning curve at the beginning. It can be somewhat challenging to install and get started."
Azure Container Registry is ranked 3rd in Container Registry with 16 reviews while JFrog Container Registry is ranked 4th in Container Registry with 2 reviews. Azure Container Registry is rated 8.2, while JFrog Container Registry is rated 8.0. The top reviewer of Azure Container Registry writes "Configurations are quite simple with tokens that set folder structure or access levels". On the other hand, the top reviewer of JFrog Container Registry writes "Acts as a central repository and comes with code scanning feature ". Azure Container Registry is most compared with Amazon ECR, Harbor, Oracle Cloud Infrastructure (OCI) and Red Hat Quay, whereas JFrog Container Registry is most compared with Harbor, Amazon ECR, Red Hat Quay and VMware Harbor Registry.
See our list of best Container Registry vendors.
We monitor all Container Registry reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
