it registers ok but here is ansible task run.
ansible-playbook -i inventories/production/hosts.yaml --limit triton pi-customize.yaml --user ansible -vv
TASK [gitlab-runner : Ensure gitlab-runner has sudo privileges without password] ***********************************************************************************************************************************************************************************************************
task path: /home/gitlab-runner/git/gitlab/penguinpages/shuffleboard/roles/gitlab-runner/tasks/main.yaml:29
ok: [triton] => {"backup": "", "changed": false, "msg": ""}
TASK [gitlab-runner : Deploy GitLab runner] ************************************************************************************************************************************************************************************************************************************************
task path: /home/gitlab-runner/git/gitlab/penguinpages/shuffleboard/roles/gitlab-runner/tasks/main.yaml:37
changed: [triton] => {"changed": true, "cmd": "sudo -u gitlab-runner gitlab-runner register -n --url https://gitlab.com --registration-token glrt-blah --executor docker --docker-image alpine:latest\n", "delta": "0:00:00.262483", "end": "2025-04-16 08:24:37.861927", "msg": "", "rc": 0, "start": "2025-04-16 08:24:37.599444", "stderr": "Runtime platform \u001b[0;m arch\u001b[0;m=arm64 os\u001b[0;m=linux pid\u001b[0;m=18228 revision\u001b[0;m=ef334dcc version\u001b[0;m=17.10.1\n\u001b[0;33mWARNING: Running in user-mode. \u001b[0;m \n\u001b[0;33mWARNING: The user-mode requires you to manually start builds processing:\u001b[0;m \n\u001b[0;33mWARNING: $ gitlab-runner run \u001b[0;m \n\u001b[0;33mWARNING: Use sudo for system-mode: \u001b[0;m \n\u001b[0;33mWARNING: $ sudo gitlab-runner... \u001b[0;m \n \u001b[0;m \n\u001b[0;33mWARNING: A runner with this system ID and token has already been registered.\u001b[0;m \nVerifying runner... is valid \u001b[0;m runner\u001b[0;m=ZzoxYnB3b\nRunner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!\n\u001b[0;m \nConfiguration (with the authentication token) was saved in \"/home/gitlab-runner/.gitlab-runner/config.toml\"\u001b[0;m ", "stderr_lines": ["Runtime platform \u001b[0;m arch\u001b[0;m=arm64 os\u001b[0;m=linux pid\u001b[0;m=18228 revision\u001b[0;m=ef334dcc version\u001b[0;m=17.10.1", "\u001b[0;33mWARNING: Running in user-mode. \u001b[0;m ", "\u001b[0;33mWARNING: The user-mode requires you to manually start builds processing:\u001b[0;m ", "\u001b[0;33mWARNING: $ gitlab-runner run \u001b[0;m ", "\u001b[0;33mWARNING: Use sudo for system-mode: \u001b[0;m ", "\u001b[0;33mWARNING: $ sudo gitlab-runner... \u001b[0;m ", " \u001b[0;m ", "\u001b[0;33mWARNING: A runner with this system ID and token has already been registered.\u001b[0;m ", "Verifying runner... is valid \u001b[0;m runner\u001b[0;m=ZzoxYnB3b", "Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!", "\u001b[0;m ", "Configuration (with the authentication token) was saved in \"/home/gitlab-runner/.gitlab-runner/config.toml\"\u001b[0;m "], "stdout": "", "stdout_lines": []}
so it registers fine. I use executor “docker” and figured I would then convert to podman per other postings. The runner registers fine. Just can’t run jobs as it can’t connect back to podman.socket because it keeps using (I think) the toml file it creates in /home/gitlab-runner/.gitlab-runner/config.toml vs the one with patch for pod man in /etc/gitlab-runner/config.toml