Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runner auto update makes the runner crash #268

Closed
kuperiudazn opened this issue Jan 21, 2021 · 3 comments
Closed

Runner auto update makes the runner crash #268

kuperiudazn opened this issue Jan 21, 2021 · 3 comments
Labels

Comments

@kuperiudazn
Copy link

kuperiudazn commented Jan 21, 2021

I'm using the controller v0.16.0 with runner v2.275.1. From this morning The runner is autoupdating to v2.276.0
Now when a job start the runner crash. I saw that there's an issue about 2.276.0 #264. But for now i'm unable to use the runner.

Is there a way to disable the runner's auto update ?

@callum-tait-pbx
Copy link
Contributor

I think there are 2 issues going on atm:

  1. There is the issues with the externals volume which an issue with this solution fixed by Fix self-update failuers due to /runner/externals mount #253 in theory
  2. There is an issue with v2.276.0 itself which is an issue with the runner project Hosted Github runner auto update to 2.276.0 fails - leaves runner in dead state runner#925

Being able to stop auto updates would be great and tbh I think a major issue with github actions atm. actions/runner#925 suggests that this isn't behaviour that can be opted out of though and would need the ability to do so added into the runner project itself

@achedeuzot
Copy link

I didn't find a way of disabling the auto-update but I did manage to restart everything by following the discussion in the PR #253.
See #264 (comment)

Indeed, being able to prevent auto-updates would be very appreciated so we don't need to quickly fix & patch a critical system such as the build/release 😄

@stale
Copy link

stale bot commented Apr 30, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 30, 2021
@stale stale bot closed this as completed May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants