Here’s the Deal

Docker Registry 2.0 vs JFrog Bintray

52 4

3 4

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 19th. The most important reason people chose Docker Registry 2.0 is:

Currently includes in-memory, local filesystem, Azure, and S3.

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best docker image private registries?

Pros

Pro
Maintains several storage drivers to allow for different models of image retention

Currently includes in-memory, local filesystem, Azure, and S3.

Pro
Simple to set up

https://docs.docker.com/registry/#basic-commands

Pro
Only supports docker images

If you want more then go somewhere else! :)

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.

Ad
Cons

Con
Biggest CON there is that it cannot control deleting of images properly

Bottom line is this makes docker registry suck when your harddisk fills up at the wrong time and you cannot push out your builds!

Con
No inbuilt access control provided

Authentication or Authorization is not provided by default and needs to be handled externally. An optional authentication should have been provided, given that docker client has inbuilt authentication.