The config.toml file is what configures a runner. You wouldn't have one unless you're running your own gitlab-runners, in which case it would be in /etc/gitlab-runner/config.toml on the host running the runner. More information on Gitlab Runner and running it yourself is available here.

Answer from Adam Marshall on Stack Overflow
🌐
GitLab
gitlab.com › gitlab.org › gitlab-runner › repository
config.toml.example · main · GitLab.org / gitlab-runner · GitLab
GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab
🌐
GitLab
docs.gitlab.com › runner › configuration › advanced-configuration
Advanced configuration | GitLab Docs
Configure this section once for all runners, not for each individual runner. # Example `config.toml` file with session server configured concurrent = 100 # A global setting for job concurrency that applies to all runner sections defined in this `config.toml` file log_level = "warning" log_format = "runner" check_interval = 3 # Value in seconds [session_server] listen_address = "[::]:8093" # Listen on all available interfaces on port `8093` advertise_address = "runner-host-name.tld:8093" session_timeout = 1800
Discussions

Gitlab: where is config.toml? - Stack Overflow
The config.toml file is what configures a runner. You wouldn't have one unless you're running your own gitlab-runners, in which case it would be in /etc/gitlab-runner/config.toml on the host running the runner. More on stackoverflow.com
🌐 stackoverflow.com
GitLab Runners - Using CICD variables in toml
Variables in the project will already be used in the environment, so in before_script, script, after_script job part. The toml file cannot read environment created during CI/CD, because it's a configuration " before" any ci/CD even start. But...why the double configuration? More on reddit.com
🌐 r/gitlab
5
2
December 12, 2023
How to use local image from docker-compose on gitlab ci
Id recommend going to r/gitlab those guys know the backend of a gitlab environment far better than we do collectively. More on reddit.com
🌐 r/devops
4
6
July 4, 2018
Gitlab runner config.toml values vs. environment vars
No, those variables are used at registration to set the values within the TOML.  For an already-registered runner, config.toml is the gospel. More on reddit.com
🌐 r/gitlab
3
2
June 12, 2025
🌐
GitHub
github.com › veertuinc › gitlab-runner › blob › master › config.toml.example
gitlab-runner/config.toml.example at master · veertuinc/gitlab-runner
May 29, 2024 - Contribute to veertuinc/gitlab-runner development by creating an account on GitHub.
Author   veertuinc
🌐
GitLab
docs.gitlab.com › runner › configuration
Configure GitLab Runner | GitLab Docs
Learn how to configure GitLab Runner. Advanced configuration options: Use the config.toml configuration file to edit runner settings.
🌐
DevOpsSchool.com
devopsschool.com › home › gitlab tutorials: understanding runner config.toml & example of config.toml
GitLab Tutorials: Understanding runner config.toml & Example of config.toml - DevOpsSchool.com
December 23, 2022 - The config.toml file is what configures a runner. You wouldn’t have one unless you’re running your own gitlab-runners, in which case it would be in /etc/gitlab/config.toml on the host running the runner.
🌐
GitHub
github.com › ayufan › gitlab-ci-multi-runner › blob › master › config.toml.example
gitlab-ci-multi-runner/config.toml.example at master · ayufan/gitlab-ci-multi-runner
August 10, 2018 - This repository is a mirror for automated DockerHub builds. Please go to: - gitlab-ci-multi-runner/config.toml.example at master · ayufan/gitlab-ci-multi-runner
Author   ayufan
Find elsewhere
🌐
Gitlab
gitlab-docs-d6a9bb.gitlab.io › install › configure gitlab runner › advanced configuration
Advanced configuration | GitLab
Configure this section once for all runners, not for each individual runner. # Example `config.toml` file with session server configured concurrent = 100 # A global setting for job concurrency that applies to all runner sections defined in this `config.toml` file log_level = "warning" log_format = "runner" check_interval = 3 # Value in seconds [session_server] listen_address = "[::]:8093" # Listen on all available interfaces on port `8093` advertise_address = "runner-host-name.tld:8093" session_timeout = 1800
🌐
Joseph Gan's Blog
bwgjoseph.com › how-to-setup-and-configure-your-own-gitlab-runner
Configure your own Gitlab runner - Joseph Gan's Blog
January 29, 2022 - As mentioned in the docs, if we do not define an image to use within gitlab-ci.yml, the default base image will be used to run the job but we can override it by specifying the image we wish to use for the job as seen in the example above · Once registered, look at docker logs and you should see this · gitlabee-runner | Configuration loaded builds=0 gitlabee-runner | Runtime platform arch=amd64 os=linux pid=8 revision=5316d4ac version=14.6.0 gitlabee-runner | Starting multi-runner from /etc/gitlab-runner/config.toml...
🌐
GitLab
docs.gitlab.com › runner › commands
GitLab Runner commands | GitLab Docs
Read from a configuration file to use a specific runner’s configuration. For example, a single job with a configuration file: gitlab-runner run-single -c ~/.gitlab-runner/config.toml -r runner-name
🌐
GitLab
docs.gitlab.com › runner › register
Registering runners | GitLab Docs
docker run --rm -v /srv/gitlab-runner/config:/etc/gitlab-runner gitlab/gitlab-runner register \ --non-interactive \ --url "https://gitlab.com" \ --token "$RUNNER_AUTHENTICATION_TOKEN" \ --template-config /tmp/test-config.template.toml \ --description "gitlab-ce-ruby-3.1" \ --executor "docker" ...
🌐
Interesting IT Tip's
interestingittips.wordpress.com › tag › config-toml
config.toml – Interesting IT Tip's
$ sudo gitlab-runner list # Answer Runtime platform arch=arm os=linux pid=19991 revision=8fa89735 version=13.6.0 Listing configured runners ConfigFile=/etc/gitlab-runner/config.toml # To verify delete $ sudo gitlab-runner verify --delete $ sudo service gitlab-runner restart # To uninstall the runner executable # sudo apt remove gitlab-runner
🌐
GitLab
docs.gitlab.com › runner › examples › gitlab.html
How to configure GitLab Runner for GitLab CE integration tests
Sign in to GitLab · Loading · By signing in you accept the Terms of Use and acknowledge the Privacy Statement and Cookie Policy · Don't have an account yet? Register now · or sign in with · Remember me · Explore Help About GitLab GitLab community forum
🌐
GitHub
github.com › gitlabhq › gitlab-runner › blob › main › config.toml.example
gitlab-runner/config.toml.example at main · gitlabhq/gitlab-runner
Mirror | Please open new issues in our issue tracker on GitLab.com - gitlab-runner/config.toml.example at main · gitlabhq/gitlab-runner
Author   gitlabhq
🌐
GitHub
gist.github.com › 93025793f1a0ebde61fbc8569fa30a34
Gitlab Runner Configuration - ~/.gitlab-runner/config.toml · GitHub
Gitlab Runner Configuration - ~/.gitlab-runner/config.toml · Raw · config.toml · This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
🌐
GitLab
docs.gitlab.com › runner › configuration › configuring_runner_operator
Configuring GitLab Runner on OpenShift | GitLab Docs
Create a custom configuration template file. For example, let’s instruct our runner to mount an EmptyDir volume and set the cpu_limit. Create the custom-config.toml file:
🌐
GitLab
docs.gitlab.com › runner
GitLab Runner | GitLab Docs
Runner configuration: A single [[runner]] entry in the config.toml that displays as a runner in the UI.
🌐
GitLab
docs.gitlab.com › runner › executors › docker
Docker executor | GitLab Docs
The following example uses Podman to build a container image and push the image to the GitLab Container registry. The default container image in the Runner config.toml is set to quay.io/podman/stable, so that the CI job uses that image to execute the included commands.
🌐
Gitlab
gitlab-org.gitlab.io › - › gitlab-docs › - › jobs › 6316549 › artifacts › public › runner › configuration › advanced-configuration.html
Sign in · GitLab
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify ...