Description
The binary syncer downloads the distribution and store the dist in S3. Cachning the binary speed-up the start process of the runner.
Problem
Historically the only option to download the latest release was getting all releases and search the latest one. Assuming this is the first non pre-release or draft. Due to re-releases and the fact the lambda is most likely not implementing pagination an to old runner version is downloaded. This can casue the runner is not starting.
I did not checked all the scenarios but a scenario that is certainly casuing a problem once you disable the auto update and use the module provided scripts to install the runner on start.
Workaround
- Build you own tailored AMI containing the distribution of the runners
- Enable the auto update of the runner (default)
- Manually update the distribution in the bucket. Ensure you use the same naming as the file you find currently in your bucket.
- Upgrade to v1.10.0
Solution
Updat the lambda, and use the release to fetch the latest release only, see #2455
Reference
See also actions/runner#2151