GitHub server does not support configuring a self-hosted runner with 'DisableUpdate' flag.
See original GitHub issueTrying to use this library with my GHE resulted in the following error message:
The GitHub server does not support configuring a self-hosted runner with 'DisableUpdate' flag.
I’m using the codebuild provider and narrowed it down to the –disableupdate flag.
I’m new to this whole topic, but removing it from by buildspec manually resolved the issue. I’m guessing that the flag might even be irrelevant anyways since the runners are ephemeral?
What are the impacts of removing that flag? could we make it optional?
Issue Analytics
- State:
- Created a year ago
- Comments:8 (5 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 >Add support for new disable update flag · Issue #1086 - GitHub
It just got shipped, we should add a new env var into the entrypoint to configure this new setting. The default should be...
Read more >Configuring the self-hosted runner application as a service
Stop the self-hosted runner application if it is currently running. · Install the service with the following command: sudo ./svc.sh install · Alternatively,...
Read more >Disable runner auto update · Issue #485 - GitHub
Describe the bug We are running the runner in docker containers and it is forcing us to update the runner and shuts it...
Read more >Autoscaling with self-hosted runners - GitHub Docs
You can automatically scale your self-hosted runners in response to webhook ... the --disableupdate flag when registering your runner using config.sh .
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
I haven’t had much time to start making the changes this weekend. i’ve just had time here and there to validate your other fixes. I don’t think i’ve ever seen someone maintaining a repo turn around my issues so fast! You are amazing!
If you are wanting to just bust this issue out too, go for it. i probably wont be able to start until tomorrow.
Side note: i was able to validate the docker changes from the other issue. I’m able to successfully run my job now!
Thanks! 😁 It’s my current passion project and it makes me happy to see bug reports come in because that’s how I know people actually use it.