Comparing the Container Registry

I’m evaluating setting up the Container Registry, using the sameersbm/docker-gitlab image which I high recommend.

Following [1] and GitLab’s own installation instructions, it’s easy to see this is quite convoluted.

So I’m asking: what’s the difference between using GitLab’s own registry vs, say, Nexus? Consider that installing Nexus is extremely straightforward to deploy using Docker (particular if you’re already deploying GitLab using it).

The things I can think of are:

  1. authentication: I don’t know whether Nexus can be made to authenticate via GitLab’s oauth2.
  2. UX integration: having a tab within GitLab seems easier for the end user.
  3. .gitlab-ci.yml would be a little more complex (should build and push manually)

– icarrera


@icarrera Being in the same situation :slight_smile:

The thing is that not only I use Nexus as docker registry as introduced in latest versions, but also as central proxy for any binary/meta data. Scenario I work in is where production systems must be disconnected from internet and I plan to use Nexus not only for services/microservices deployment (Java), but also for Docker (as you mentioned) and lastly for RPM packages, python/perl packages, and others when supported.

So with nexus I can have all under one cover, but also being iterested what is PROS going with Gitlab feature here…

Sorry, didn’t provide any answer as I didn’t tested yet Gitlab docker registry capabilitites.


I facing the same scenario and interested to get hints and tips how to solve it.

Without more details about the specific problem you’re facing, and what you have tried so far, I don’t think you’ll get any responses. If you can expand on your situation (a great deal) that may help encourage replies.