From 52628dcff92ce432e4adcfa9b959d564ff8afd49 Mon Sep 17 00:00:00 2001 From: Abubakar Siddiq Ango Date: Mon, 11 Feb 2019 09:19:08 +0000 Subject: [PATCH] Update on using self-signed certs with registry --- doc/administration/container_registry.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/doc/administration/container_registry.md b/doc/administration/container_registry.md index db0b3e1270c..975d9025b09 100644 --- a/doc/administration/container_registry.md +++ b/doc/administration/container_registry.md @@ -600,9 +600,16 @@ The Docker daemon running the command expects a cert signed by a recognized CA, thus the error above. While GitLab doesn't support using self-signed certificates with Container -Registry out of the box, it is possible to make it work if you follow -[Docker's documentation][docker-insecure-self-signed]. You may find some additional -information in [issue 18239][ce-18239]. +Registry out of the box, it is possible to make it work by [instructing the docker-daemon to trust the self-signed certificates][docker-insecure-self-signed], mounting the docker-daemon and setting `privileged = false` in the runner's `config.toml`. Setting `privileged = true` takes precedence over the docker-daemon. + +``` + [runners.docker] + image = "ruby:2.1" + privileged = false + volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/cache"] +``` + +You may find some additional information in [issue 18239][ce-18239]. ## Troubleshooting