<!-- END doctoc generated TOC please keep comment here to allow auto update -->
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
## Configuration
## Assumptions
Containers can be large in size and they are stored on the server GitLab is
If you are using Omnibus, you have to bare in mind the following:
installed on.
The Container Registry works under HTTPS by default.
- The container Registry will be enabled by default if GitLab is configured
This means that the Container Registry requires a SSL certificate.
with HTTPS and it will listen on port `5005`. If you want the Registry to
There are two options on how this can be configured:
listen on a port other than `5005` which is the default, read [#Container Registry under existing GitLab domain](#container-registry-under-existing-gitlab-domain)
on how to achieve that. You will also have to configure your firewall to allow
connections to that port.
- The Container Registry works under HTTPS by default. Note that using HTTP is
possible but not recommended and out of the scope of this document,
[see the insecure Registry documentation][docker-insecure] if you want to
implement this.
1. Use its own domain - needs a SSL certificate for that specific domain
## Container Registry domain configuration
(eg. registry.example.com) or a wildcard certificate if hosted under a subdomain
(eg. registry.gitlab.example.com)
1. Use the existing GitLab domain and expose the registry on a port - can reuse
existing GitLab SSL certificate
Note that using HTTP is possible but not recommended,
There are two ways you can configure the container Registry domain. Either use