Repository navigation
Conversation
|
Awesome work as usual @mumoshu ! Do you want me to test this or you're confident with your tests? |
|
JFY: I tested this pull request as int128/actions-runner-controller-in-actions#6.
|
|
I hope this would be an official image for RunnerScaleSets. We tried |
|
Switch from Debian to Ubuntu 22.04 actions/runner#2651 |
|
Hello. |
|
Pending testing |
|
I really like both old and new setups, but in the new setup I do miss the option to run dind in a single image and be able to set precise requests and limits for the whole thing. |
- `should_work_use_disable_once_switch` was failing since the support for --once has been removed a while ago. Removed the test. - Added `cd` before running `startup.sh` for access to the logger.sh library from within the script - Included the runner directory into `$PATH` for access to `update-status` from within the script
74617c1 to
fb1a7cc
Compare
Hi! I made our current runner images work with the new RunnerScaleSet.
Let me share how so everyone can try and figure out how to build custom runner images that contain more tools and software you like 👋
I'm submitting this as a pull request because it doesn't break our current runner images and is worth merging for a better experience migrating to the new ARC!
There are only a few differences between the new and the current runner images.
TL;DR; We can add some dockerfile build args and envs and make the part that calls
config.shto be conditional and that's all you need to make it work with RunnerScaleSet.Here are the differences:
/runner/home/runner/runner/externalstmp/home/runner/externalsexternalsfor dind sidecarcpcpAnd apparently, the changes introduced via this pull request is all you need to make it work for both.
You can build e.g., an Ubuntu 20.04 runner image that seems to work with the new RunnerScaleSet by overriding some paths via new build args added in this PR: