'launchctl' failed: exit status 112, Could not find domain for

The following relate to troubleshooting on macOS. SessionCreate KeepAlive SuccessfulExit RunAtLoad Disabled Label -runner UserName gitlab GroupName staff ProgramArguments /usr/local/opt/gitlab-runner/bin/gitlab-runner run -working-directory /Users/gitlab/gitlab-runner -config /Users/gitlab/gitlab-runner/config.toml -service gitlab-runner -syslog EnvironmentVariables PATH /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin macOS troubleshooting

If Homebrew was used to install git, it may have added a /usr/local/etc/gitconfig file You can verify that GitLab Runner created the service configuration file afterĮxecuting the install command, by checking the Run the Runner’s service as a LaunchDaemon, but this mode of operation is not LaunchDaemons are run on system startup, but theyĭon’t have the same access to UI interactions as LaunchAgents. It’s worth noting that macOS also has LaunchDaemons, services runningĬompletely in background. The builds are able to perform UI interactions, making it possible to run and The service is launched as a LaunchAgent. You can obtain your username by running the command ls /users.Ĭurrently, the only proven way for it to work in macOS is by running the service in user-mode.īecause the service runs only when the user is logged in, you should enable auto-login on your macOS machine. To sign in as your current user, run the command su - in the terminal.

The service needs to be installed from a Terminal window logged inĪs your current user.

For mac download Company of Crime