runner-images
terraform-aws-github-runner
runner-images | terraform-aws-github-runner | |
---|---|---|
51 | 17 | |
9,113 | 2,350 | |
2.5% | 4.1% | |
9.8 | 9.5 | |
1 day ago | 3 days ago | |
PowerShell | HCL | |
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
-
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)
- steam run problem after install. missing depedencies
- VM Scale Set in Running Status but Failed Provisioning state...leaving agent jobs queued with "No agents in pool VMSS-Prod are currently able to service this request."
- [HELP] Building Unity WebGL projects in Azure Devops CI/CD pipeline
terraform-aws-github-runner
- Show HN: Managed GitHub Actions Runners for AWS
- Show HN: Open-source x64 and Arm GitHub runners. Reduces GitHub Actions bill 10x
- Terraform module for scalable GitHub action runners on AWS
- Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
- Any tips on how to run auto scaling self-hosted GitLab runners well?
- Auto scaling Self-Hosted solution for GitHub Actions?
-
DeepFlow uses Spot Instances to speed up GitHub Action exploration
Terraform: Autoscale AWS EC2 as GitHub Runner with Terraform and AWS Lambda
What are some alternatives?
jellyscrub - Smooth mouse-over video scrubbing previews for Jellyfin.
workflow-dispatch - A GitHub Action for triggering workflows, using the `workflow_dispatch` event
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
terraform-aws-oidc-github - Terraform module to configure GitHub Actions as an IAM OIDC identity provider in AWS.
json-tidy - Pretty prints JSON from stdin, files, or URLs
sst - Build modern full-stack applications on AWS
changed-files - :octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
aws-toolkit-vscode - Amazon Q, CodeWhisperer, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
combine-prs-workflow - Combine/group together PRs (for example from Dependabot and similar services)
serverless-iam-roles-per-function - Serverless Plugin for easily defining IAM roles per function via the use of iamRoleStatements at the function level.
just - 🤖 Just a command runner
serverless-bonk-template - Serverless boilerplate based on serverless-webpack + typescript.