DevOps / Gitlab Interview questions
What is the difference between GitLab Container Registry and Docker Hub?
Both store and serve Docker-compatible container images, but they differ in where they sit relative to your source code and how access control is managed.
| GitLab Container Registry | Docker Hub |
| Built into each GitLab project automatically. | A separate, standalone registry service. |
| Access controlled by the project's existing permissions. | Access controlled by Docker Hub's own account/org system. |
| Private images included at no extra registry-specific cost. | Free tier limits private repositories; paid plans needed for more. |
| Tightly integrated with GitLab CI/CD (push/pull without extra credentials setup). | Requires configuring separate registry credentials in any CI system. |
Docker Hub is the default public registry most base images (like node, python, nginx) come from, so most teams still pull from Docker Hub even while pushing their own built images to GitLab's registry. They're commonly used together rather than as a strict either/or choice.
GitLab Container Registry's access control is based on:
Most public base images like node or nginx are typically pulled from:
More Related questions...
