When comparing Docker Registry 2.0 vs JFrog Bintray, the Slant community recommends Docker Registry 2.0 for most people. In the question“What are the best docker image private registries?” Docker Registry 2.0 is ranked 2nd while JFrog Bintray is ranked 7th. The most important reason people chose Docker Registry 2.0 is:
Ranked in these QuestionsQuestion Ranking
Pro Simple to set up
Pro Maintains several storage drivers to allow for different models of image retention
Currently includes in-memory, local filesystem, Azure, and S3.
Pro 100% Automated via REST API
Open for automation, JFrog Bintray easily integrates with your existing DevOps ecosystem, such as your continuous integration pipeline and your internal repositories. A rich REST API allows you to control every aspect of your software distribution, manage who has access to your content, collect logs and analytics, and much more - all with the full automation expected of a modern software distribution platform.
Pro Statistics and dashboards
Great statistics on downloads of your Docker images according to tags, geo-location and more..
Pro Universal solution
One distribution platform that supports all technologies. JFrog Bintray natively supports all major package formats, which allows you to work seamlessly with industry standard development, build and deployment tools. With support for massive scalability and worldwide coverage, this gives you the best native repository distribution available.
Pro Full control and security
Exercise fine-grained access control over who can view, upload to or download from your private repositories. Maintain any degree of control through a variety of means, such as IP and geographical restrictions, EULA acceptance and more. Automatically provision your organization users via API, or have them silently sign in with SAML authentication to your existing identity provider.
Con Only supports docker images
Con Sometimes images disappear
Con Setting it up may require some work
Setting up the new Docker Registry 2.0 requires some more setup than usual. Especially dependencies need to be installed beforehand.