New runner registration - reusing token is causing the runner to be replaced, not added

GitLab CI/CD
1

According to documentation, reusing the authentication token will result in each runner that uses it being added to the “parent” runner shown in Group → CI/CD → Runners as another actual runner with a different system ID.

Yet when I attempt to add a new runner using that authentication token, it REPLACES the runner, which is directly observable by the IP address changing on the single runner shown, instead of a new runner being added.

According to this documentation, each runner using the same authentication token should be added.

gitlab-runner register --non-interactive -url “https://gitlab.com” --token “glrt-t2_tokenstring” --executor “docker” --docker-image “alpine:latest” --description “manual test” --cache-shared=true --cache-type = “s3” --cache-s3-bucket-name “bucketname” --cache-s3-server-side-encryption “s3” --cache-s3-bucket-location “us-east-1”

Versions

Please select whether options apply, and add the version information.

  • Self-managed
  • [x ] GitLab.com SaaS
  • Dedicated
  • Self-hosted Runners
2

According to the link you provided, but this section that I’ve marked: Plan and operate a fleet of instance or group runners | GitLab

your command is using the docker executor, so I believe for you to be able to achieve what you are doing, you need to first have a runner manager using the docker-machine executor - since in the part you linked it says:

So, once the first runner-manager is registered, with the authentication token, and subsequent runners are registered also with that same authentication token, they should then be grouped as you are expecting them to be.

At least that is how I understand the documentation.

3

The message about docker-machine being deprecated lead me to this page:

Which is exactly what I needed.

Thank you, appreciate the help!

1 Like