I have the same issue. I’m using a custom image built on top of the base one, and every time a new version of the base image is released, runners try to auto-update and then exit with an error.

√ Connected to GitHub

2020-09-15 18:11:56Z: Runner reconnected.
2020-09-15 18:11:56Z: Listening for Jobs
Runner update in progress, do not shutdown runner.
Downloading 2.273.2 runner
Waiting for current job finish running.
Generate and execute update script.
Runner will exit shortly for update, should back online within 10 seconds.
/runner/run.sh: line 47: /runner/bin/Runner.Listener: No such file or directory

There are some possible solutions proposed above:

• https://github.community/t/options-to-prevent-auto-updating-self-hosted-runner/17046/5
• https://github.com/summerwind/actions-runner-controller/issues/33#issuecomment-625876718
• https://github.com/actions/runner/issues/484#issuecomment-630154371

I’ll try to integrate one of them and open a PR.

When I looked into the code, I couldn’t find a way to stop self-updating. I’ve created the following Issue. https://github.com/actions/runner/issues/431

I’ll also look into how to make self-updating a success.

@igorbrigadir thanks a ton for entrypoint hint, implemented here https://github.com/summerwind/actions-runner-controller/pull/99 . Worked like a charm.

I’ve been experiencing similar issues - also using a custom image and also having to update manually every time there’s a new release. In my case however, i’ve been making other breaking changes so it took me a while to pin it down to something wrong with the runner.

It would be fantastic if this was fixed, as it defeats the purpose of self hosted runners (having to manually tend to them after updates). This one https://github.com/actions/runner/issues/484#issuecomment-630154371 seems to be the best way to me.

Thank you for using and reporting! I think that this is a self-hosted runner’s default behavior. Let me find out how to stop self-updating.