Add Ssl Certificate To Docker Container



  • Install the Docker image and start the container

This is how you can run GitLab Runner inside a Docker container.

General GitLab Runner Docker image usage

I ran into the same issue when trying to do a pull from a private registry. I tried to install the certificate on the client and didn’t work, so I deleted it, then I realized that if I stop the docker service that is running as a systemd service, and start the docker daemon by hand with dockerd, I’m able to download the images. I am trying to add certificate Authority (CA) file name - ca.crt to /etc/ssl/certs, for that I followed this article. Docker container ssl certificates.

GitLab Runner Docker images (based on Ubuntu or Alpine Linux)are designed as wrappers around the standard gitlab-runner command, like ifGitLab Runner was installed directly on the host.

The Apache HTTP Server Project. I have a Linux-based Docker container, where if I do: curl I get an error: curl: (60) SSL certificate problem: self signed certificate in certificate chain More de.

The general rule is that every GitLab Runner command that normally would be executedas:

can be executed with:

For example, getting the top-level help information for GitLab Runner command could beexecuted as:

In short, the gitlab-runner part of the command is replaced withdocker run [docker options] gitlab/gitlab-runner, while the rest of thecommand stays as it is described in the register documentation.The only difference is that the gitlab-runner command is executed inside of aDocker container.

Install the Docker image and start the container

Before you begin, ensure Docker is installed.

To run gitlab-runner inside a Docker container, you need to make sure that the configuration is not lost when the container is restarted. To do this, there are two options, which are described below.

Make sure that you read the FAQ section which describes some of the most common problems with GitLab Runner.

If you are using a session_server, you will also need to expose port 8093 by adding -p 8093:8093 to your docker run command.

Option 1: Use local system volume mounts to start the Runner container

This example uses the local system for the configuration volume that is mounted into the gitlab-runner container. This volume is used for configs and other resources.

Option 2: Use Docker volumes to start the Runner container

In this example, you can use a configuration container to mount your custom data volume.

  1. Create the Docker volume:

  2. Start the GitLab Runner container using the volume we just created:

To set the container’s timezone, in the docker run command, use the flag --env TZ=<TIMEZONE>. View a list of available time zones.

Register the runner

The final step is to register a new runner. The GitLab Runner Container won’t pick up any jobs until it’s registered.

Update configuration

If you change the configuration in config.toml, you might need to restart the runner to apply the change.Make sure to restart the whole container instead of using gitlab-runner restart:

Upgrade version

Pull the latest version (or a specific tag):

Stop and remove the existing container:

Start the container as you did originally:

You need to use the same method for mounting you data volume as youdid originally (-v /srv/gitlab-runner/config:/etc/gitlab-runner or--volumes-from gitlab-runner-config).

Add Ssl Certificate To Windows Docker Container

Reading GitLab Runner logs

When GitLab Runner is started as a foreground task (whether it’s a locally installed binary orinside of a Docker Container), the logs are printed to the standard output. WhenGitLab Runner is started as a system service (e.g. with Systemd), the logs are in mostcases logged through Syslog or other system logging mechanism.

With GitLab Runner started as a Docker based service, since the gitlab-runner ... command isthe main process of the container, the logs can be read using the docker logs command.

For example, if GitLab Runner was started with the following command:

Add ssl certificate to docker container search

you may get the logs with:

Add Ssl Certificate To Docker Container Availability

Add

where gitlab-runner is the name of the container, set with --name gitlab-runner bythe first command.

You may find more information about handling container logs at the Docker documentationpage.

Installing trusted SSL server certificates

If your GitLab CI server is using self-signed SSL certificates then you shouldmake sure the GitLab CI server certificate is trusted by the GitLab Runnercontainer for them to be able to talk to each other.

The gitlab/gitlab-runner image is configured to look for the trusted SSLcertificates at /etc/gitlab-runner/certs/ca.crt, this can however be changed using the-e 'CA_CERTIFICATES_PATH=/DIR/CERT' configuration option.

Add ssl certificate to docker container availability

Copy the ca.crt file into the certs directory on the data volume (or container).The ca.crt file should contain the root certificates of all the servers youwant GitLab Runner to trust. The GitLab Runner container willimport the ca.crt file on startup so if your container is already running youmay need to restart it for the changes to take effect.

Docker images

The following multi-platform Docker images are available:

  • gitlab/gitlab-runner:latest based on Ubuntu.
  • gitlab/gitlab-runner:alpine based on Alpine with much a smaller footprint(~160/350 MB Ubuntu vs ~45/130 MB Alpine compressed/decompressed).

See GitLab Runnersource for possible build instructions for both Ubuntu and Alpine images.

The IBM Z image does not contain the docker-machine dependency, as it is not yet maintained for the Linux s390xplatform. See issue for current status.

SELinux

Some distributions (CentOS, RedHat, Fedora) use SELinux by default to enhance the security of the underlying system.

Special care must be taken when dealing with such a configuration.

  1. If you want to use the Docker executor to run builds in containers, you’ll need access to /var/run/docker.sock.However, if SELinux is in enforcing mode, you will see a Permission denied error when you’re accessing /var/run/docker.sock.Install selinux-dockersock to resolve this issue.
  2. Make sure that a persistent directory is created on host: mkdir -p /srv/gitlab-runner/config.
  3. Run Docker with :Z on volumes:

More information about the cause and resolution can be found here:http://www.projectatomic.io/blog/2015/06/using-volumes-with-docker-can-cause-problems-with-selinux/

Help & feedback

Docs
Edit this pageto fix an error or add an improvement in a merge request.
Create an issueto suggest an improvement to this page.
Show and post commentsto review and give feedback about this page.
Product
Create an issueif there's something you don't like about this feature.
Propose functionalityby submitting a feature request.
Join First Lookto help shape new features.
Feature availability and product trials
View pricingto see all GitLab tiers and features, or to upgrade.
Try GitLab for freewith access to all features for 30 days.
Get Help

If you didn't find what you were looking for,search the docs.

Add ssl certificate to windows docker container

If you want help with something specific and could use community support,post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLabsubscription).

Request supportPlease enable JavaScript to view thecomments powered by Disqus.