You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are shipping by default in the module scripts tuned for Amazon Linux and with some extra configuration Ubuntu can be used. But since GitHub is standard relying on Ubuntu several actions are not working on Amazon Linux. Or sometime updates of actions.are not fully supported out of the box.
By changing de standard configured linux version to Ubuntu we keep the module closer to the GitHub standard hosted runners. With extra configuration you can still adjust the Linux version
Once implemented this will trigger a major release.
Implementations directions
Adjust scripts based on Ubuntu example.
Update the launch templates default to Ubuntu
Replace ubuntu example by an Amazon Linux one
Update multi-runner examples
Docs update
Other
Help, suggestions and feedback is welcome.
The text was updated successfully, but these errors were encountered:
Hi, I've updated the Ubuntu example in mutli-runner to work correctly on my PR.
That should give you a starting point.
I'd also suggest making the choice between rootless and rootful docker a configuration option, especially for ephemeral nodes (I realise this is a security risk so default to rootless).
Description
Currently we are shipping by default in the module scripts tuned for Amazon Linux and with some extra configuration Ubuntu can be used. But since GitHub is standard relying on Ubuntu several actions are not working on Amazon Linux. Or sometime updates of actions.are not fully supported out of the box.
By changing de standard configured linux version to Ubuntu we keep the module closer to the GitHub standard hosted runners. With extra configuration you can still adjust the Linux version
Once implemented this will trigger a major release.
Implementations directions
Other
Help, suggestions and feedback is welcome.
The text was updated successfully, but these errors were encountered: