Unsure what value to pass to $TOKEN for registering the runner (./config.sh)

[erictaur]

Describe the bug
Unsure what value to pass to $TOKEN for registering the runner

To Reproduce
Steps to reproduce the behavior:
Follow the setup guide in the antmicro/runner README

# Sudo into the runner user
sudo -i -u runner bash
cd /home/runner/github-actions-runner

# Modified file is listed at the end of the issue for reference
cp .vm_specs.example.json .vm_specs.json
vim .vm_specs.json

# Register the runner in the desired repository.
export SLOTS=1
./config.sh --url https://github.com/idea-fasoc/OpenFASOC --token $TOKEN --num $SLOTS

Expected behavior
Able to register the repo to the gha-main runner service.

Runner Version and Platform

Everything is grabbed from the vm-runner branch of antmicro/runner

OS of the machine running the runner?

GCP e2-medium (2 vCPUs, 4 GB memory)

What's not working?

./config.sh cannot be run out of the box.

Currently attempted fixes:

• Unsure what to pass to $TOKEN, passing an arbitrary value leads to an infinite loop
• _layout directory not found (Currently commented out)

Current status of vm_specs.json

runner@gha-runner-coordinator:~/github-actions-runner$ cat .vm_specs.json
{
  "gcp": {
    "type": "e2-medium",
    "disk_type": "pd-ssd",
    "zone": "us-west1-a",
    "project": "catx-ext-umich",
    "subnet": "default",
    "image": "debian-10-buster-v20210916",
    "sa": "[email protected]"
  },
  "machine": {
    "disk": 10
  }
}

Installation script is believed to be executed successfully since supervisord and the gha-main@ service is detectable by the system.

Job Log Output

N/A

Runner and Worker's Diagnostic Logs

N/A

FYI @msaligane

[AdamOlech]

Hey @erictaur, you need to pass the token obtained from the Runners settings page (which is located in the settings tab of a repository). I added this information to README.

In your case, this page should be located at https://github.com/idea-fasoc/OpenFASOC/settings/actions/runners/new (be mindful that you need to have administrative privileges to the repository).

Let me know if that solves your issue.