GitLab Runner: Introduction

This documentation is part of the Building Docker images guide. You can view the complete guide here: Build and push Docker images efficiently from your GitLab CI/CD pipelines using Stackhero runners and Docker-in-Docker.

👋 Welcome to the Stackhero documentation!

Stackhero offers you an easy-to-use GitLab Runner cloud solution, designed to efficiently run your GitLab CI/CD jobs. Here’s what you can benefit from:

• Unlimited CI/CD minutes: there’s no per-minute billing, so your pipelines can run whenever you need them.
• Concurrent jobs: run multiple jobs in parallel to speed up your entire pipeline.
• The Docker executor with Docker-in-Docker support: simplify building and pushing your container images.
• Compatible with GitLab.com as well as any self-managed GitLab instance.
• A private, dedicated VM powered by fast NVMe/SSD disks for reliable, consistent builds.
• Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

Save time: connect your first GitLab Runner and start running pipelines in just a few minutes!

With a Stackhero GitLab Runner, each job runs inside an isolated container using the Docker executor. You can build your own Docker images directly within your pipeline by enabling Docker-in-Docker (DinD). This configuration starts a Docker daemon alongside your job, allowing you to run docker build and docker push commands as part of your CI/CD process.

Every run benefits from unlimited CI/CD minutes: you are free to trigger as many builds as you need, without worrying about quotas. Your build cache is stored on the runner's dedicated disk, enabling reuse of previous layers for repeated builds. This significantly reduces build times and speeds up your pipelines.