Omnibus Docker image for GitLab does not have docker registry working by default

When trying to setup GitLab using the omnibus docker image, the docker registry in GitLab is not active by default.

Following the directions on https://docs.gitlab.com/omnibus/docker/, there is no docker registry (5000) port exposed. Further, after launching GitLab from the docker image, in the admin panel, the registry is not turned on. According to the docs (https://docs.gitlab.com/ee/administration/packages/container_registry.html), as of 12.5, the registry should be turned on by default.

The documentation for using the Omnibus Docker image should be updated to reflect access to the registry. Additionally, it appears that some bug exists that prevents the registry from being turned on by default.

added documentation grouppackage registry typebug labels

added Category:Omnibus Package label

@joshlambert @ljlane I think this issue is related to: omnibus-gitlab#4690 (closed)

Thanks @trizzi. I added labels to get this triaged by groupdistribution

added devopssystems groupdistribution labels and removed grouppackage registry label

mentioned in issue #211307 (closed)

mentioned in issue #212131 (closed)

mentioned in issue #213512 (closed)

mentioned in issue #214201 (closed)

mentioned in issue #214972 (closed)

mentioned in issue #215838 (closed)

mentioned in issue #216432 (closed)

mentioned in issue #217291 (closed)

mentioned in issue #218212 (closed)

mentioned in issue #218955 (closed)

mentioned in issue #219707 (closed)

mentioned in issue #220741 (closed)

mentioned in issue #222242 (closed)

mentioned in issue #223664 (closed)

mentioned in issue #225141 (closed)

mentioned in issue #226969 (closed)

mentioned in issue #230666 (closed)

mentioned in issue #232389 (closed)

mentioned in issue #233343 (closed)

mentioned in issue #235098 (closed)

mentioned in issue #237836 (closed)

mentioned in issue #240867 (closed)

mentioned in issue #243480 (closed)

added sectioncore platform label

mentioned in issue #246472 (closed)

mentioned in issue #249074 (closed)

mentioned in issue #254175 (closed)

mentioned in issue #257800 (closed)

mentioned in issue #262006 (closed)

mentioned in issue gitlab-org/quality/triage-reports#503 (closed)

mentioned in issue gitlab-org/quality/triage-reports#561 (closed)

mentioned in issue gitlab-org/quality/triage-reports#637 (closed)

mentioned in issue gitlab-org/quality/triage-reports#702 (closed)

mentioned in issue gitlab-org/quality/triage-reports#735 (closed)

mentioned in issue gitlab-org/quality/triage-reports#823 (closed)

mentioned in issue gitlab-org/quality/triage-reports#864 (closed)

mentioned in issue gitlab-org/quality/triage-reports#935 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1013 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1094 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1200 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1251 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1362 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1400 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1526 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1561 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1674 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1776 (closed)

added vintage label

Hi @sethgitlab ,

Thanks for raising this bug.

Contributions like this are vital to help make GitLab a better product.

We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.

This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.

Thanks for your contributions to make GitLab better!

Hi @gitlab-bot

I don't know if this issue is still present, however, since no one else that has commented on this issue in a year, I think it's safe to close out.

added stale label

closed