Commit 52628dcf authored by Abubakar Siddiq Ango's avatar Abubakar Siddiq Ango

Update on using self-signed certs with registry

parent 1a1f28fe
...@@ -600,9 +600,16 @@ The Docker daemon running the command expects a cert signed by a recognized CA, ...@@ -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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment