1
Step 1Open the server Apps tab
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.
Back to all templates
GitLab Runner
Infrastructure256MB+ RAM
CI/CD runner for GitLab pipelines
ci-cdgitlabrunner
Deploy GitLab Runner in 3 Steps
1
Connect Your VPS
Add your server credentials to Server Compass
2
Select GitLab Runner
Choose from our template library
3
Deploy & Configure
Fill in settings and click Deploy
No Docker knowledge required
Step-by-step deployment guide
Deploy GitLab Runner on a VPS with Server Compass
Use the GitLab Runner template in Server Compass to deploy a clean, ready-to-register GitLab CI runner service on your VPS, then verify the runner container, version output, and generated config.
About 10 minutesBrowser verified
2
Step 2Choose an app template
Click New App and choose the template deployment path so Server Compass can load the built-in catalog.
3
Step 3Search for GitLab Runner
Use the template picker search to find GitLab Runner in the Server Compass template catalog.
4
Step 4Select the GitLab Runner template
Choose the GitLab Runner template. Server Compass fills the one-shot config bootstrap service, the runner service, the persistent config volume, and the Docker socket mount.
5
Step 5Review the GitLab Runner settings
Confirm the app name and compose services. In this run, the app was named gitlab-runner-demo; GitLab Runner does not expose a public web port by default.
6
Step 6Deploy GitLab Runner
Review the generated compose settings, confirm the config bootstrap and runner services, and click Deploy.
7
Step 7Watch the deployment progress
Keep the deployment modal open while Server Compass uploads the compose file, pulls the GitLab Runner image, starts the container, and verifies the stack.
8
Step 8Confirm GitLab Runner is running
After deployment finishes, return to the Apps tab and confirm the GitLab Runner app is marked Running.
9
Step 9Verify GitLab Runner from the container
Verify the runner container is running, the config bootstrap completed, the GitLab Runner version command works, and the logs show the configuration loaded cleanly.
After GitLab Runner Opens
- Register the runner with a GitLab project, group, or instance registration token.
- Choose the executor, tags, and protected-runner settings for trusted workloads only.
- Avoid sharing this runner with untrusted public projects because it has Docker socket access.
- Back up the runner_config volume if you need to preserve the registered runner configuration.
Verified Result
The runner container was running, the config bootstrap exited successfully, `gitlab-runner --version` returned a version, and logs showed `Configuration loaded` without missing-config errors.
GitLab Runner deployment questions
What does the GitLab Runner template deploy?
It deploys a one-shot config bootstrap service and the official GitLab Runner container with persistent runner configuration and Docker socket access.
Which port did the tutorial use?
GitLab Runner does not expose a public web port in this template. Verification happens through container status, version output, config file checks, and recent logs.
Does GitLab Runner need setup after deployment?
Yes. The template starts the service cleanly with an initial config file, then you register the runner with GitLab using a project, group, or instance registration token.
Should this become a blog post?
No. The deployment guide should live on the GitLab Runner template detail page and be linked from the reusable template deployment docs page.
Do It Yourself
Deploy GitLab Runner via Command Line
Prefer the command line? Follow this step-by-step guide to deploy GitLab Runner manually on your VPS.
1
Connect to Your Remote Server
Begin by establishing a secure connection to your server through the terminal.
terminal
# Access your VPS
ssh root@YOUR_SERVER_IP
# With SSH key authentication
ssh -i ~/.ssh/your-private-key root@YOUR_SERVER_IPFirst time? Ensure Docker is installed first: curl -fsSL https://get.docker.com | sh
2
Set Up Your App Folder
Create a dedicated folder for your application files.
terminal
# Create and navigate to project directory
mkdir -p ~/apps/gitlab-runner
cd ~/apps/gitlab-runner3
Set Up Docker Compose
Create the following docker-compose.yml in your project directory:
docker-compose.yml
services:
gitlab-runner:
image: gitlab/gitlab-runner:latest
volumes:
- runner_config:/etc/gitlab-runner
- /var/run/docker.sock:/var/run/docker.sock
restart: unless-stopped
volumes:
runner_config:
4
Spin Up the Stack
Run Docker Compose to launch your application.
terminal
# Launch the stack
docker compose up -d
# Verify container status
docker compose ps
# Follow the logs
docker compose logs --follow5
Open the Application Port
Configure UFW to allow traffic to your application.
terminal
# Allow the application port through firewall
sudo ufw allow 80/tcp
sudo ufw reload
# Access your app at:
# http://your-server-ip:80Skip the Terminal
Make it simple with Server Compass.
Deploy GitLab Runner with a beautiful UI instead. No SSH, no YAML editing, no terminal commands. Just click, configure, and deploy in under 3 minutes.
- No terminal required
- Point-and-click setup
- Auto SSL certificates
- Rolling deployments
- Health monitoring
- Instant rollbacks
Download Server Compass$29 one-time • Lifetime license
After Deployment
After deploying GitLab Runner with Server Compass, complete these steps to finish setup
1
Register runner with GitLab
2
Configure executor
3
Add runner tags
Need help? Check out our documentation for detailed guides.
GitLab Runner FAQ
Common questions about self-hosting GitLab Runner
How do I deploy GitLab Runner with Server Compass?
Simply download Server Compass, connect to your VPS, and select GitLab Runner from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
What are the system requirements for GitLab Runner?
GitLab Runner requires a minimum of 256MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Can I migrate my existing GitLab Runner data?
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard GitLab Runner backup and restore procedures.
How do I update GitLab Runner to the latest version?
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest GitLab Runner image will be pulled and deployed with zero downtime.
Is GitLab Runner free to self-host?
GitLab Runner is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.
Ready to Self-Host GitLab Runner?
Download Server Compass and deploy GitLab Runner to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass