-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat: 22.04 default runner image #2050
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
Conversation
mumoshu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect. Thanks as always for your awesome work
This synchronizes our image with GitHub hosted runners, which are moving to Ubuntu 22.04: https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/. See also the rationale at actions/actions-runner-controller#2050.
|
Hi, Any possibility to include back |
|
Hello, same here, I think we are using the summerwind image though, but we're seeing |
|
Removing build-essential has broken a load of our CI/CD workflows that use |
Depends on #2036 #2063
Resolves #2006
To Do
Preample
A new Ubuntu version represents an opportunity for the ARC maintainers to cut down on the installed software in the runner. The existing runner images contain a lot of sofware that would not typically be needed in CI/CD environment or has a niche use case, by including it we get the following negatives:
The software that is included in the runner as it is today was largely inherited and not active choices made by the current maintainers.
Things Removed and Why
build-essential - CI/CD unrelated / niche use case
dnsutils - CI/CD unrelated
ftp - CI/CD unrelated / niche use case
iproute2 - CI/CD unrelated
iputils-ping - CI/CD unrelated
libunwind8 - CI/CD unrelated
locales - CI/CD unrelated
netcat - CI/CD unrelated
openssh-client - CI/CD unrelated / niche use case
parallel - niche use case
rsync - CI/CD unrelated / niche use case
shellcheck - various actions exist to run shellcheck, too opinionated to be in the base runner https://github.com/search?q=shellcheck+action https://github.com/github/super-linter
telnet - CI/CD unrelated
time - CI/CD unrelated
tzdata - CI/CD unrelated
upx - CI/CD unrelated
wget - we already bundle curl which covers the same use case
zstd - CI/CD unrelated
Python
python - there is a official set-up action for Python so no need to bundle it making the base image larger https://github.com/actions/setup-python
python3-pip - python has been removed
When our runner images were first produced GitHub Actions offered very poor support for managing runners and so there was a strong incentive for ARC to have a fatter more inclusive image over a slimmer image. Since those days GitHub has introduced the
--disableupdateflag enabling ARC administrators to more easily use their own runners built from ours without significant operational impacts lessening the incentive to bundle as much as possible in the ARC runners themselves.