runner-images
runner
runner-images | runner | |
---|---|---|
54 | 59 | |
9,292 | 4,612 | |
2.3% | 2.5% | |
9.8 | 9.0 | |
5 days ago | 3 days ago | |
PowerShell | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
runner-images
- GitHub Actions are randomly failing
-
Creating new Perl composite actions from a repository template
So you want to create a quick-and-dirty GitHub actions that does only one thing and does it well, or glues together several actions, or simply to show off a bit at your next work interview. Here's how you can do it. Let me introduce you to composite GitHub actions, one of the three types that are there (the other are JavaScript GHAs or container-based GHAs) and maybe one of the most widely unknown. However, they have several things going for them. First, they have low latency: no need to download a container or to set up some JS environment). Second, they are relatively easy to set up: they can be self-contained, with everything needed running directly on the description of the GitHub action. Third, you can leverage all the tools installed on the runner like bash, compilers, build tools... or Perl, which can be that and much more. Even being easy, it is even easier if you have a bit of boilerplate you can use directly or adapt to your own purposes. This is what has guided the creation of the template for a composite GitHub action based on Perl. It is quite minimalistic. But let me walk you through what it has got so that you can use it easier
-
Github Actions to deploy your Terraform code
I used the “ubuntu-latest” image which is Debian-based (with apt) and commonly available in the Github Actions workers, so it deploys very fast.
-
Show HN: Managed GitHub Actions Runners for AWS
Yeah this is a good option if you'd like something to deploy yourself! You can also build an AMI from GitHub's upstream image definition (https://github.com/actions/runner-images/tree/main/images/ub...) if you'd like it to match what's available in GitHub-hosted Actions.
With Depot, we're moving towards deeper performance optimizations and observability than vanilla GitHub runners - we've integrated the runners with a cache storage cluster for instance, and we're working on deeper integration with the compute platform that we built for distributed container image builds - as well as expanding the types of builds we can process beyond Actions and Docker, for instance.
But different options will be better for different folks, and the `philips-labs` project is good at what it does.
- GitHub switched to Docker Compose v2, action needed
-
We Executed a Critical Supply Chain Attack on PyTorch
Whoa, there's a lot of stuff in there [1] that gets installed straight from vendors, without pinning content checksums to a value known-good to Github.
I get it, they want to have the latest versions instead of depending on how long Ubuntu (or, worse, Debian) package maintainers take to package stuff into their mainline repositories... but this attack surface is nuts.
[1] https://github.com/actions/runner-images/tree/main/images/ub...
-
Terraform module for scalable GitHub action runners on AWS
I had a similar experience with ARC (actions-runner-controller).
One of the machines in the fleet failed to sync its clock via NTP. Once a job X got scheduled to it, the runner pod failed authentication due to incorrect clock time, and then the whole ARC system started to behave incorrectly: job X was stuck without runners, until another workflow job Y was created, and then X got run but Y became stuck. There were also other wierd behaviors like this so I eventually rebuilt everything based on VMs and stopped using ARC.
Using VMs also allowed me to support the use of the official runner images [0], which is good for compatibility.
I feel more people would benefit from managed "self-hosted" runners, so I started DimeRun [1] to provide cheaper GHA runners for people who don't have the time/willingness to troubleshoot low-level infra issues.
[0]: https://github.com/actions/runner-images
- Apple Silicon (M1) powered macOS runners are now available in public beta
-
macOS Containers v0.0.1
Reminds me: Still waiting for native ARM support on GitHub Actions https://github.com/actions/runner-images/issues/5631
-
Question on using Linux Self Hosted Agents with VMSS
Used https://github.com/actions/runner-images to get the packages needed for Ubuntu 22.04 As the packer requires a builder, I used "null" builder to set it as localhost ref: https://developer.hashicorp.com/packer/docs/builders/null (It was way difficult to figure it out the 1st time) I had to modify the .pkr.hcl file to pick my provisioners. I could not understand the use of /opt/hostedtoolcache folder (which I did later)
runner
- 20-line PR to add key Docker feature to GitHub Actions, please upvote
-
Why the fuck are we templating YAML? (2019)
In the case of GitHub Actions, it's made more painful by the lack of support for YAML anchors, which provide a bare minimum of composability.
https://github.com/actions/runner/issues/1182
- please dont state this as a "workaround". your version simply "pretends" it is a tty when infact it is not an actual tty
-
PySide vs. .NET WinForms for a Desktop GUI App in 2023?
Even if you don’t pick Avalonia, their notes for Mac distribution look useful:
https://docs.avaloniaui.net/docs/distribution-publishing/mac...
For example, the GitHub actions runner itself is a modern .NET core project with CI except for .app packaging.
https://github.com/actions/runner/tree/main/.github/workflow...
-
GitHub Actions Are a Problem
This probably answers your question:
https://github.com/actions/runner/blob/a4c57f27477077e57545a...
-
DevOps CI/CD Quick Start Guide with GitHub Actions 🛠️🐙⚡️
$ mkdir actions-runner && cd actions-runner $ curl -o actions-runner-osx-arm64-2.311.0.tar.gz -L https://github.com/actions/runner/releases/download/v2.311.0/actions-runner-osx-arm64-2.311.0.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 98.1M 100 98.1M 0 0 20.0M 0 0:00:04 0:00:04 --:--:-- 23.5M $ echo "fa2f107dbce709807bae014fb3121f5dbe106211b6bbe3484c41e3b30828d6b2 actions-runner-osx-arm64-2.311.0.tar.gz" | shasum -a 256 -c actions-runner-osx-arm64-2.311.0.tar.gz: OK $ tar xzf ./actions-runner-osx-arm64-2.311.0.tar.gz ❯ ./config.sh --url https://github.com/dpills/devops-quick-start-guide --token AGDCRGCMZWN34QIVISIO5XXXXXX -------------------------------------------------------------------------------- | ____ _ _ _ _ _ _ _ _ | | / ___(_) |_| | | |_ _| |__ / \ ___| |_(_) ___ _ __ ___ | | | | _| | __| |_| | | | | '_ \ / _ \ / __| __| |/ _ \| '_ \/ __| | | | |_| | | |_| _ | |_| | |_) | / ___ \ (__| |_| | (_) | | | \__ \ | | \____|_|\__|_| |_|\__,_|_.__/ /_/ \_\___|\__|_|\___/|_| |_|___/ | | | | Self-hosted runner registration | | | -------------------------------------------------------------------------------- # Authentication √ Connected to GitHub # Runner Registration Enter the name of the runner group to add this runner to: [press Enter for Default] Enter the name of runner: [press Enter for dpills-mac] This runner will have the following labels: 'self-hosted', 'macOS', 'ARM64' Enter any additional labels (ex. label-1,label-2): [press Enter to skip] √ Runner successfully added √ Runner connection is good # Runner settings Enter name of work folder: [press Enter for _work] √ Settings Saved. ❯ ./run.sh √ Connected to GitHub Current runner version: '2.311.0' 2023-10-27 13:32:16Z: Listening for Jobs
-
Automate Flutter app delivery to AppCenter with GitHub Actions
A runner is where your action's jobs will be run. It can be a hosted virtual environment, or you can self-host a runner in your machine.
- GitHub Actions Frequently Failing
- Runners fail to set up job with tar -xzf error
-
How to deal with MSVC in DevOps
If i understand this writing correctly (https://github.com/actions/runner/issues/904), running Windows containers in a windows-latest GH Actions host is not possible. While using a self-hosted runner on a Windows server might be an option, this is not what I want since it is a package repo for a well-known open source project, think of the package repo part as a mini-Conan. I wouldn't know who would want to host that. In the best case we would stay with just GH Actions to keep everything confined in one space :)
What are some alternatives?
jellyscrub - Smooth mouse-over video scrubbing previews for Jellyfin.
act - Run your GitHub Actions locally 🚀
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
azure-pipelines-agent - Azure Pipelines Agent 🚀
changed-files - :octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
virtual-environments - GitHub Actions runner images [Moved to: https://github.com/actions/runner-images]
json-tidy - Pretty prints JSON from stdin, files, or URLs
github-act-runner - act as self-hosted runner
combine-prs-workflow - Combine/group together PRs (for example from Dependabot and similar services)
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
just - 🤖 Just a command runner
docker-github-runner-linux - Repository for building a self hosted GitHub runner as a ubuntu linux container