: Change the downloaded file name to gitlab-runner.exe .
docker run -d --name gitlab-runner --restart always \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /srv/gitlab-runner/config:/etc/gitlab-runner \ gitlab/gitlab-runner:latest ``` --- ### 2. Registering Your Runner Once installed, you must connect the runner to your GitLab instance so it can receive jobs. 1. **Get Your Token**: Go to your project or group in GitLab, navigate to **Settings > CI/CD**, and expand the **Runners** section to find your registration token. 2. **Run Register Command**: On your runner machine, execute: ```bash gitlab-runner register ``` 3. **Follow Prompts**: * **GitLab Instance URL**: Use `https://gitlab.com` or your self-hosted URL. * **Registration Token**: Paste the token from Step 1. * **Description/Tags**: Enter a name and tags (used to target specific jobs to this runner). * **Executor**: Choose `docker`, `shell`, or `ssh`. For most modern CI/CD, **docker** is the recommended choice. --- ### 3. Why Use Self-Managed Runners? While GitLab provides hosted runners, installing your own offers several advantages: * **Custom Infrastructure**: Use specific hardware (GPUs, macOS) or internal network resources. * **Cost Control**: Avoid consuming GitLab's shared runner minutes on paid plans. * **Security**: Keep your build environment and sensitive data within your own firewall. * **Performance**: Run multiple jobs concurrently and use local caching to speed up builds. Would you like help choosing the right **executor type** (e.g., Docker vs. Shell) for your specific project requirements? Use code with caution. Install GitLab Runner download runner gitlab
You can run the runner inside a container to avoid local installation: : Change the downloaded file name to gitlab-runner
The most common way to download and stay updated on Linux is using the GitLab Official Repositories : : **Run Register Command**: On your runner machine, execute: