Disable runner auto update
See original GitHub issueDescribe the bug We are running the runner in docker containers and it is forcing us to update the runner and shuts it down.
Is there any way we can disable this?
https://github.com/ydataai/docker-github-runner -> project with the Dockerfile to build runner in containers
To Reproduce
- Go to the folder where you have github-runner
- execute ./run.sh
- Run a job
Expected behavior I want to run the runner without it forcing me to update and shutting down my docker
Runner Version and Platform
Version of your runner? v2.169.1
OS of the machine running the runner? Linux
Job Log Output
github@acace520a67a:~$ tail -f runner.log
√ Connected to GitHub
2020-05-18 16:21:01Z: Listening for Jobs
Runner update in progress, do not shutdown runner.
Downloading 2.262.1 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 and Worker’s Diagnostic Logs
Doesn’t seem relevant.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:68
- Comments:30 (6 by maintainers)
Top Results From Across the Web
Self-hosted runners can now disable automatic updates
You now have more control over when your self-hosted runners perform software updates. If you specify the --disableupdate flag to the runner ......
Read more >Can I disable Auto Update (for example, while running tests)?
In order to prevent the Auto Update check, run the application with the netbeans.full.hack system property set to true . For example, use...
Read more >How to auto update github action runner
GitHub Actions Runner should update itself automatically unless you passed the --disableupdate command line parameter to config.sh .
Read more >How do I disable automatic updates for the Duo Device ...
Users can disable automatic updates in the Preferences section of Duo Device Health application (DHA) on an individual basis. If you want to...
Read more >Disable auto-updates for the OS? : r/Chromecast
Settings>System>About>System Software Update. Then you should see (on the right side of the screen) two choices. Software Update and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Every time an update is released, my kube runners go into a crash loop backoff. 😦
It’s not about being interactive or not, it’s about user features, if for some reason i want to be stuck on that runner version, no matter the reason, i think that’s up to me, right?
I’m not saying that it should be as this, but it’s an odd behaviour, if i have that image tagged with the version of the runner, it will loose sense then. What if the update breaks, that runner will be down and that’s not cool. And this internal self update is something that shouldn’t happen in a container, that’s why it was nice to have a flag to disable it.
And svc.sh it attached to systemd cli and we would prefer to not have it in the machine.
Thanks for the info, feel free to close the issue.