GitLab Runner: Introduction

This documentation is part of the Building Docker images guide. View the full 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 gives you an easy-to-use GitLab Runner cloud solution designed to handle your GitLab CI/CD jobs efficiently. Here is what you can look forward to:

• Unlimited CI/CD minutes: there is no per-minute billing, so your pipelines can run whenever you need them.
• Multiple concurrent jobs: run several jobs at the same time to speed up your entire pipeline.
• The Docker executor with Docker-in-Docker support: streamline 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 consistent, reliable builds.
• Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

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

With a Stackhero GitLab Runner, every job runs inside a fresh container using the Docker executor. You can build your own Docker images directly in your pipeline by enabling Docker-in-Docker (DinD). This setup launches a Docker daemon alongside your job, so you are able 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 build as often as needed, without worrying about usage limits. Your build cache is stored on the runner's dedicated disk, which means repeated builds can reuse previous layers. This significantly reduces build times and helps your pipelines complete faster.