-
We’re trying to run self-hosted runners inside our kubernetes cluster, it worked fine until our image didn’t contain the latest runner: Runner update in progress, do not shutdown runner.Downloading 2.161.0 runner I know that runner will automatically update to latest version and exit for a while. However, this update would fail every time and exit, resulting in kubernetes spinning up another Pod, which finally we see an infinite loop.Is there an option to disable such behavior in ./run.sh? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Have you configured your self-hosted runner as a service? Configure the self-hosted runner as a service can avoid automatic update failures. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply, but it seems that running as service didn’t help, is it something to do with container/kubernetes environment? This is output:
|
Beta Was this translation helpful? Give feedback.
-
We figured out there was something wrong with our WORKDIR settings, which cannot be root folder in this case. |
Beta Was this translation helpful? Give feedback.
Have you configured your self-hosted runner as a service? Configure the self-hosted runner as a service can avoid automatic update failures.
You can reference this earlier reported ticket: https://github.community/t5/GitHub-Actions/self-hosted-runner-update-protocol/td-p/37930