Setting Up the Runner with Jacamar

Establishing, registering, and starting the runner, executing Jacamar, is done automatically by the host container upon spinup of the Jacamar Docker-Compose service.

On spinup, the container entrypoint for the service non-interactively registers, and starts the runner. On spindown, the container automatically unregisters the runner.

This means that, before the Jacamar service is spun up, The GDK needs to have finished booting within the Gitlab service. This can be verified by navigating to the address serving the Gitlab instance you are attempting to register with, and verifying that you can log in as the root.

Further, this means that the HOSTNAME and RUNNER_REGISTRATION_TOKEN variables in the .env file located at the root of this project’s repo, must be properly set. The HOSTNAME variable is valid so long as it was not changed between the start of the Gitlab service and the start of the Jacamar service. The RUNNER_REGISTRATION_TOKEN can be accessed on a per instance basis under the Runner section of the Gitlab instance admin panel at Admin –> Runners , or on a per project basis under CI/CD –> Runners. This value must be set corrently in the .env file before running

$ docker-compose up -d jacamar

Note:

If a new user is required on the gitlab side, a mirroring user must be created in the jacamar-runner host container. More info can be found in the Adding a user to Runner section.