GitHub Actions Runner Images
Table of Contents
- About
- Available Images
- Image Definitions
- Image Releases
- [Software and Image guidelines]
- [How to interact with this Repo]
- [FAQs]
About
This repository contains the source used to create the runner images for GitHub Actions hosted runners, as well as the VM images of Microsoft-hosted agents used for Azure Pipelines. To build a VM machine from this repo's source, see the instructions.
Available Images
| Image | YAML Label | Included Software | Latest Release & Rollout Progress |
|---|---|---|---|
| Ubuntu 20.04 | ubuntu-latest or ubuntu-20.04 |
ubuntu-20.04 | |
| Ubuntu 18.04 | ubuntu-18.04 |
ubuntu-18.04 | |
| macOS 11 | macos-latest or macos-11 |
macOS-11 | |
| macOS 10.15 | macos-10.15 |
macOS-10.15 | |
| Windows Server 2022 | windows-latest or windows-2022 |
windows-2022 | |
| Windows Server 2019 | windows-2019 |
windows-2019 | |
| Windows Server 2016 | windows-2016 |
windows-2016 |
Image Definitions
Beta:
The purpose of a Beta is to collect feedback on an image before it is released to GA. The goal of a Beta is to identify and fix any potential issues that exist on that image. Images are updated on a weekly cadence. Any workflows that run on a beta image do not fall under the customer SLA in place for Actions. Customers choosing to use Beta images are encouraged to provide feedback in the runner-images repo by creating an issue. A Beta may take on different availability, i.e. public vs private.
GA:
A GA (General Availability) image has been through a Beta period and is deemed ready for general use. Images are updated on a weekly cadence. In order to be moved to GA the image must meet the following criteria: 1- Has been through a Beta period (public or private) 2- Most major software we install on the image has a compatible version for the underlying OS and 3- All major bugs reported during the Beta period have been addressed. This image type falls under the customer SLA for actions. GA images are eventually deprecated according to our guidelines as we only support the latest 2 versions of an OS.
Image Releases
Cadence We typically deploy weekly updates to the software on the runner images.
Following Along
- High Impact Changes (ex. breaking changes, new or deprecated images) will be posted to the GitHub Changelog on our blog and on twitter.
- Low Impact Changes will be pinned in this repository and marked with the Announcement label.
- Regular Weekly Rhythm can be followed by watching Releases. A pre-release is created when deployment is started. As soon as deployment is finished, it is converted to a release. You can also track upcoming changes using the awaiting-deployment label.
Software and image guidelines
To learn more about tools and images support policy, see the guidelines.
How to interact with this repo
- To file a bug report, or request tools to be added/updated, please open an issue using the appropriate template
- If you want to share your thoughts about image configuration, installed software, or bring some idea, please, create a new topic in a discussions section for a corresponding category. Before making a new discussion please make sure no similar topics were created earlier.
For general questions about using the runner images or writing your Actions workflow, please open requests in the GitHub Actions Community Forum.
FAQs
What images are available for GitHub Actions and Azure DevOps? The availability of images for GitHub Actions and Azure DevOps is different. See documentation for more details:
What image version is used in my build? Usually, image deployment takes 3-4 days, and documentation in the main branch is only updated when deployment is finished. To find out which image version and what software versions are used in a specific build, see Set up job (GitHub Actions) or Initialize job (Azure DevOps) step log.
Looking for other Linux distributions? We do not plan to offer other Linux distributions. We recommend using Docker if you'd like to build using other distributions with the hosted runner images. Alternatively, you can leverage self-hosted runners and fully customize your VM image to your needs.
How do I contribute to the macOS source? macOS source lives in this repository and is available for everyone. However, macOS image-generation CI doesn't support external contributions yet so we are not able to accept pull-requests for now. We are in the process of preparing macOS CI to accept contributions. Until then, we appreciate your patience and ask you to continue to make tool requests by filing issues.
How do GitHub determine what tools are installed on the images? For some tools, we always install the latest at the time of the deployment; for others, we pin the tool to specific version(s). ( needs more details)