https://clarence.tw/en/notes/gitlab/ Recent content in GitLab on Clarence | Backend, AI, DevOps, Infrastructure Hugo -- gohugo.io en Mon, 26 Oct 2026 00:00:00 +0800 https://clarence.tw/en/notes/gitlab/runner-config/ Mon, 26 Oct 2026 00:00:00 +0800 https://clarence.tw/en/notes/gitlab/runner-config/ <section class="note-card " aria-labelledby="note-section-version-and-safety-scope-2"> <div class="item"> <h2 class="note-title" id="note-section-version-and-safety-scope-2"><span>Version and safety scope</span></h2> <div class="card"> <div class="card-body"><p><strong>Last reviewed: October 26, 2026</strong></p> <p>Checked against the official GitLab documentation on October 26, 2026, when the latest GitLab Runner release was v19.5.1. Settings and defaults change between versions; before production use, check <a href="https://docs.gitlab.com/runner/configuration/advanced-configuration/" target="_blank" rel="noopener">Runner advanced configuration</a>, <a href="https://docs.gitlab.com/runner/register/" target="_blank" rel="noopener">Registering runners</a>, and <a href="https://docs.gitlab.com/ci/variables/predefined_variables/" target="_blank" rel="noopener">Predefined CI/CD variables</a>.</p> <p><code>privileged = true</code>, mounting <code>/var/run/docker.sock</code>, <code>gitlab-runner unregister</code>, and <code>gitlab-runner verify --delete</code> carry security or irreversible risks and are flagged below. Back up <code>config.toml</code> before changing it. Runner tokens and registry passwords are secrets; keep them out of repositories and CI logs.</p>