fix: add `jq`, `git`, `unzip` and `curl` to default packages installed
Hi 👋🏼
I am using this runner with the Actions Runner Controller
These three packages are used by a ton of actions on the marketplace. It would be nice if they were installed and ready for use instead of having to install them with apt-get on every single Github workflow. If using more than one job in a workflow you have to have a step to install these in each one.
I know you all probably want to keep a low footprint of installed tools but these are probably just as important as sudo for user experience.
Will also fix https://github.com/actions/actions-runner-controller/issues/3222
any update on this?
as some people already asked, is there any update on this?
The silence from the action/runners maintainers is deafening 😭
There's probably some huge philosophical debate behind closed doors:
- the practical: yeah, this makes sense
- the minimalist: they'd have it be a clone of
scratchif they could get away with it
I'm starting to wonder if the project is maintained. I mean, I clearly see them merging PRs but only their own PRs and without much context/comments on them. They don't seem to be interested in community contributions or building this with the community.
It's probably based on business driven development, meaning paying customers who want changes are prioritized. 😢
Honestly it seems to be community doesn't matter for them))
The decision behind our slim image was to:
provide a small image that can be used to execute workflows in case you don't need extra tools
Except you can't execute any workflows because not even git is installed... for a GitHub builder...
This is funny... https://github.com/actions/runner/pull/3273
👋🏼 @TingluoHuang is this purposely getting ignored?
any news on this?
@omri-shilton (or anyone else) if the company you work for has a support contract with GitHub, bring this up in a ticket. My assumptions are it doesn't look like individual contributors PRs are prioritized unless there's a push from a GitHub customer.
There have been other issues created about how bare the self hosted runner image is. It doesn't seem like a priority for github. Doesn't seem like they're willing to budge on this unfortunately.
https://github.com/actions/runner/issues/3080
I think there was a discussion post about it somewhere too.
If I had a tinfoil hat 👽 at this point: they want your first jobs to fail so that you don't use self-hosted runners. We all know that a greater barrier to entry means less people will use it. /s
Sorry for the tumbleweeds, let me poke the team and get someone to look at this.
Updated.
We have to spend ~20s each build installing git - this would be such a great change 🙏
@nebuk89 @TingluoHuang any update?
instead of having to install them with apt-get on every single Github workflow. If using more than one job in a workflow you have to have a step to install these in each one.
@onedr0p why not use your own runner image with all the packages you need already installed?
I already do that but it wouldn't be required for me to maintain if the GitHub runner included Git by default.
I will follow up!
🥇
I really love this update!!
When will this change be included in a patch release v2.319.2? Still experiencing issues with this.