When comparing Gitlab Container Registry vs JFrog Bintray, the Slant community recommends Gitlab Container Registry for most people. In the question“What are the best docker image private registries?” Gitlab Container Registry is ranked 1st while JFrog Bintray is ranked 19th. The most important reason people chose Gitlab Container Registry is:
Good integration into the repository you build your docker images out of. Just activate it for your repo and you're done. Most of the time new projects/repo have it on by default.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Integration into GitLab
Good integration into the repository you build your docker images out of. Just activate it for your repo and you're done. Most of the time new projects/repo have it on by default.
Pro Free
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 Tight integration into GitLab
If you're not building your docker images via GitLab CI, it's kinda hard to push images to the registry.
Con Docker garbage collection
Gitlab has very poor docker garbage collection management by default. One must read a good portion of the documentation to know what to do, so that garbage collection kicks in.