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
Self update failed due to /externals
mount point
#252
Comments
@e36-cicd Thanks for reporting! This hurts. Probably the update process has been changed since we added /runner/externals to your containers for compatibility with GH's managed runners? The only way I could come up was to make Here's the part of your Dockerfile that instructs docker to bake those under Probably we need to update it to extract files under e.g. |
* Fix self-update failuers due to /runner/externals mount Fixes #252 * Tested Self-update Fixes (#269) Adding fixes to #253 as confirmed and tested in #264 (comment) by @jolestar, @achedeuzot and @hfuss 🙇 🍻 Co-authored-by: Hayden Fuss <wifu1234@gmail.com>
Hi,
We ran into this issue - whenever it tries to handle a job, it detects it needs to auto update and then crashes at the end. After adding a
sleep 3600
at the end, we were able to catch it.Crash logs:
Self update failed log:
So it seems that due to the
/runner/externals
mount caused it to fail because it's an emptyDir mount so it can't be moved... Any ideas on how to fix?Thanks!
The text was updated successfully, but these errors were encountered: