kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Update on using self-signed certs with registry

This commit is contained in:
Abubakar Siddiq Ango 2019-02-11 09:19:08 +00:00
parent 1a1f28fe2a
commit 52628dcff9
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/administration/container_registry.md
View File

@ -600,9 +600,16 @@ The Docker daemon running the command expects a cert signed by a recognized CA,
thus the error above. thus the error above.
While GitLab doesn't support using self-signed certificates with Container 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 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.
[Docker's documentation][docker-insecure-self-signed]. You may find some additional
information in [issue 18239][ce-18239]. ```
[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 ## Troubleshooting