I am trying to configure a gitlab-runner on macos to use with a self hosted install.
When I install without sudo the service runs but the error log is filled with fetching jobs failed messages and ‘no route to host’. That would suggest an obvious problem except…
When I install with sudo and --user the fetching jobs step works fine and the runner picks up and executes jobs, except that it fails to upload artifacts complaining ‘no route to host’. So, there is now a route to host for checking for jobs but not for uploading artifacts.
Even more peculiar, if I don’t run it as a service at all and instead use gitlab-runner run then it both picks up jobs and uploads artifacts without complaining about route to host at all.
Versions
Please select whether options apply, and add the version information.
[X ] Self-managed
Versions
GitLab 17.2
macOS 15.0 beta (which might have something to do with it?)
The same situation after updating to MacOS 15 with gitlab-runner as service.
In the logs of gitlab-runner - no route to host.
In the system logs -
2024-09-27 09:22:39.216757+0300 0x44891 Info 0x0 199 0 nehelper: [com.apple.networkextension:] No team ID found for (bundleID: a.out, name: gitlab-runner)
2024-09-27 09:22:39.220514+0300 0x44890 Info 0x0 199 0 nehelper: [com.apple.networkextension:] Local network allowed by preference for gitlab-runner (a.out)
2024-09-27 09:22:39.224402+0300 0x4475f Default 0x0 199 0 nehelper: [com.apple.networkextension:] Local network allowed by preference for gitlab-runner (a.out), but received prompt. Clearing cached UUIDs and restarting session.
2024-09-27 09:22:39.238548+0300 0x44762 Info 0x0 149 0 nesessionmanager: (libsystem_networkextension.dylib) [com.apple.networkextension:] UUID cache ignored for a.out, path is set: /usr/local/bin/gitlab-runner
2024-09-27 09:22:39.238883+0300 0x44890 Error 0x0 199 0 nehelper: (NetworkExtension) [com.apple.networkextension:] +[NEProcessInfo copyUUIDsForExecutable:]_block_invoke: failed to get UUIDs for /usr/local/bin/gitlab-runner