My config.toml: concurrent = 1 ] name = "Docker Runner" url = "" token = "xxx" executor = "docker" tls-ca-file = "/etc/docker/certs.d//ca. (I can login to my registry and generally pull/push images, so I know my SSL certs are fine). If you are using GitLab Runner Helm chart, you will need to configure certificates according to the doc Providing a custom certificate for. gitlab-ci.yml file, set the CI variable GITSSLNOVERIFY to true. As a temporary and insecure workaround, to skip the verification of certificates, in the variables: section of your. So my build output can be seen on my gitlab: - I'm trying to fix the $ docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN Error response from daemon: Get : x509: certificate signed by unknown authorityĮssentially, I know that docker needs to have my CA cert, but I can't figure out how I give to the runner (or the docker dind container that the runner is using). If you are updating the certificate for an existing Runner, restart it. I'm sure there is a step that I'm missing - and I've spent many an hour trying to figure out how this all glues together. What I can't seem to do is get the runner to login (or push) to the registry (and thus I can't push my product build in the registry automatically). I have a private registry (now gitlab 8.8) with which I am using my own SSL certificates. In a test or development environment, you can generate your own CA. In a production environment, you should obtain a certificate from a CA. Generate a Certificate Authority Certificate. ![]() Hi, I've just started out on my first gitlab-ci setup, and I'm having some problems (but I am in awe of how great this is.) The procedures below assume that your Harbor registry’s hostname is, and that its DNS record points to the host on which you are running Harbor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |