Problem to solve
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?)