In gitlab.rb or gitlab.yml if you are using Omnibus GitLab or installedīe careful to choose a port different than the one that Registry listens to ( 5000 by default), Registry is exposed to the outside world is 4567, here is what you need to set If the Registry is configured to use the existing GitLab domain, you canĮxpose the Registry on a port so that you can reuse the existing GitLab TLSĪssuming that the GitLab domain is and the port the Configure Container Registry under an existing GitLab domain
Please take this into consideration before configuring the Container Registryįor the first time. Since the container Registry requires a TLS certificate, in the end it all boilsĭown to how easy or pricey is to get a new one.
There are two ways you can configure the Registry's external domain. If auth is not set up, users will be able to pull docker images without authentication.
Has container_registry as the service and Īs the realm: auth: token: realm: service: container_registry issuer: gitlab-issuer rootcertbundle: /root/certs/certbundle
How to install gitlab with nonbundled nginx how to#
Read the upstream documentation on how to achieve that.Īt the absolute minimum, make sure your Registry configuration Hence, restarting GitLab will not restart the Registry should Read the token auth configuration documentation.Ī Registry init file is not shipped with GitLab if you install it from source. This should be the same value as configured in Registry's issuer. Read more in #container-registry-storage-path. This path needs to be readable by the GitLab user, the web-server user and the Registry user. Read the storage configuration documentation. This should be the same directory like specified in Registry's rootdirectory. Read the token auth configuration documentation. The private key location that is a pair of Registry's rootcertbundle. The internal API URL under which the Registry is exposed to. The port under which the external Registry domain will listen on. The host URL under which the Registry will run and the users will be able to use. The contents of gitlab.yml are: registry: enabled: true host: port: 5005 api_url: key: config/registry.key path: shared/registry issuer: gitlab-issuer Lib/support/nginx/registry-ssl and edit it to match the Use the sample NGINX configuration file that is found under.Settings in gitlab.yml in order to enable it. After the installation is complete, you will have to configure the Registry's.You will have to install Registry by yourself.If you have installed GitLab from source: Read the insecure Registry documentation if you want to Using HTTP is possibleīut not recommended and out of the scope of this document. The container registry works under HTTPS by default. You can read more about the Container Registry atĪll you have to do is configure the domain name under which the ContainerĪnd pick one of the two options that fits your case. With the Container Registry integrated into GitLab, every project can have its This document is about the admin guide.Container Registry manifest v1 support was added in GitLab 8.9 to support.
0 kommentar(er)
