When comparing Docker Hub vs JFrog Bintray, the Slant community recommends Docker Hub for most people. In the question“What are the best docker image private registries?” Docker Hub is ranked 15th while JFrog Bintray is ranked 19th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Shares user accounts with the dominant public registry, Docker Hub
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.
Cons
Con No longer free
Rate limits on downloads can royally screw your deployments. In 2021, they will start deleting containers which haven't been pulled for six months. This will suck for stable software which doesn't get redeployed frequently.
Con Gives no metadata about image tags beyond their name
No information about when the image was created, pushed, what Dockerfile it came from, what user(s) pushed it, etc.
Con Poor user interface design
Con Default to public makes it dangerous
Since by default your account will create new repositories publicly, you could fairly easily leak sensitive images with one bad push.
