Contents
Is there a docker image for GitLab Runner?
GitLab Runner Docker images (based on Ubuntu or Alpine Linux) are designed as wrappers around the standard gitlab-runner command, like if GitLab Runner was installed directly on the host. The general rule is that every GitLab Runner command that normally would be executed as:
What do I need to run GitLab Runner in a container?
The ca.crt file should contain the root certificates of all the servers you want GitLab Runner to trust. The GitLab Runner container imports the ca.crt file on startup so if your container is already running you may need to restart it for the changes to take effect.
Why is GitLab omitted in Docker config.yml?
If you don’t specify the namespace, Docker implies library which includes all official images. That’s why you’ll see many times the library part omitted in .gitlab-ci.yml and config.toml . For example you can define an image like image: ruby:2.6, which is a shortcut for image: library/ruby:2.6 .
Which is the best configuration for Docker executor?
Below is an example of the configuration for a simple Docker executor running Windows. For other configuration options for the Docker executor, see the advanced configuration section. You can use services by enabling network per-build networking mode. Available since GitLab Runner 12.9. The Docker executor divides the job into multiple steps:
Where to find root certificate in GitLab Runner?
The ca.crt file should contain the root certificates of all the servers you want GitLab Runner to trust. The GitLab Runner container will import the ca.crt file on startup so if your container is already running you may need to restart it for the changes to take effect.
What kind of server do I need to run Docker?
To store our source code, run CI/CD tasks, and host the Docker registry, we need a GitLab instance installed on an Ubuntu 16.04 server. GitLab currently recommends a server with at least 2 CPU cores and 4GB of RAM. Additionally, we’ll secure the server with SSL certificates from Let’s Encrypt.