gitlab-runner-fargate's Introduction

Gitlab Runner Fargate

Usage

Setup Fargate

Create a Fargate Cluster

aws ecs create-cluster --cluster-name gitlab-runner-cluster

Register a Task Definition

Replace https://gitlab.com if you're using a self-hosted GitLab Instance
Replace $REGISTRATION_TOKEN with your own Gitlab runner registration token
Update the CPU and memory values if you wish, make sure it's a supported configuration

aws ecs register-task-definition --family gitlab-runner \
--container-definitions "[{\"name\": \"gitlab-runner-instance\",\"image\": \"woodjme/gitlab-runner-fargate\",\"environment\": [{\"name\": \"CI_SERVER_URL\", \"value\": \"https://gitlab.com\"},{\"name\": \"REGISTRATION_TOKEN\", \"value\": \"$REGISTRATION_TOKEN\"},{\"name\": \"RUNNER_NAME\", \"value\": \"fargate\"}]}]" \
--network-mode "awsvpc" \
--requires-compatibilities FARGATE \
--cpu "1024" \
--memory "2048"

Create a Service

You need to replace subnet-xyz with a subnet in your account. You can get this quick with aws ec2 describe-subnets --query 'Subnets[0].SubnetId'

aws ecs create-service --cluster gitlab-runner-cluster \
--service-name gitlab-runner-service \
--task-definition gitlab-runner \
--desired-count 1 \
--launch-type "FARGATE" \
--network-configuration "awsvpcConfiguration={subnets=[subnet-xyz],assignPublicIp=ENABLED}"

Once the service starts you should see a registered runner in GitLab

Limitations

Fargate cannot run in privileged mode so running using a Docker executor isn't possible, this means docker builds and pushes can't be done from within these runners.

Recommend Projects