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 a straightforward GitLab Runner cloud solution that makes running your GitLab CI/CD jobs efficient and hassle-free. Here’s what you can expect:

• Unlimited CI/CD minutes: run your pipelines as often as you need, with no per-minute billing or unexpected charges.
• Multiple concurrent jobs: speed up your development by running several jobs in parallel.
• The Docker executor with Docker-in-Docker support: easily build and push container images as part of your CI/CD process.
• Works seamlessly with both GitLab.com and self-managed GitLab instances.
• A private, dedicated infrastructure with fast NVMe/SSD storage ensures stable and predictable build performance.
• Available in 🇪🇺 Europe and 🇺🇸 USA regions to meet your team’s requirements.

Save time: you can 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.

Each 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, which enables reuse of previous layers for repeated builds. This significantly reduces build times and speeds up your pipelines.