runner-images

It's come up here in a few comments before. Perhaps not 100% physically shared infra but there's references of architecture overlap such as "The GitHub-hosted runner application is a fork of the Azure Pipelines Agent." https://docs.github.com/en/actions/concepts/runners/github-h... https://github.com/actions/runner-images#about A few threads where blips have affected both services. https://news.ycombinator.com/item?id=42781922 https://news.ycombinator.com/item?id=41001040 https://news.ycombinator.com/item?id=35003741

After troubleshooting a couple issues with the GitHub Actions Linux admin team, and their decision to not address either issue, I'm highly skeptical of investing more in GitHub Actions: - Ubuntu useradd command causes 30s+ hang [1] - Ubuntu: sudo -u some-user unexpectedly ends up with environment variables for the runner [2] 1: https://github.com/actions/runner-images/issues/13048 2: https://github.com/actions/runner-images/issues/13049

> That's my hill to die on : you must have a self hosted agent. That’s only true if you’re building simple workflows. A counter-example would be a workflow that builds and uploads Android APKs. When I last checked last year, there weren't any well-maintained Docker images with the Android SDK pre-installed, and there are no updated, publicly available builds for the runner-images: https://github.com/actions/runner-images/issues/176

if it's useful, they do actually have arm workers now for linux and mac: https://github.com/actions/runner-images/tree/main?tab=readm...

The best free CI system in the world has macOS 15 runners running at 75% capacity due to a background process that consumes 100% CPU [1]. The problem is known to them since May but not fixed half a year later. [1] https://github.com/actions/runner-images/issues/13358

See the docs[1] where it mentions that 10 is supported, but not available in the built-in Ubuntu feed. It however is/should become available in the backports feed. To make matters even more interesting the GitHub / Azure DevOps CI agent image Ubuntu 24.04 doesn't provide .NET 9, whereas 22.04 does[2]. .NET 10 appears to become available in both though[3]. [1]: https://learn.microsoft.com/en-gb/dotnet/core/install/linux-... [2]: https://github.com/actions/runner-images/issues/12697 [3]: https://github.com/actions/runner-images/pull/13295

Hmm yea with a self hosted runner this could work. Gotta need to set the dockerd config into the VM before the runner starts I assume - unfortunately GitHub itself does not allow to change anything for the prepare stage - and it's a known issue for 2 years at least... https://github.com/actions/runner-images/issues/1445#issueco... https://github.com/orgs/community/discussions/76636

For self-use author has a point, but for public-facing sites not so much, because: - infra work is thankless (see below) - outages will last long because you're unlikely to have failovers (for disk failures, etc.), plus the time to react to these (no point in being paged for hobby work) - more importantly, malicious LLM scrapers will put your infra under stress, and - if you host large executable you'll likely want to do things like banning Microsoft's IP address because of irresponsible GH Actions users [1] [2] [3] In the end it is just a lot less stress to pay someone else to deal with infra; for example, when hosting static sites on GH Pages or CF Pages, and when using CF caching solutions. [1] https://www.theregister.com/2023/06/28/microsofts_github_gmp... [2] https://news.ycombinator.com/item?id=36380325 [3] https://github.com/action

Sorry for the late reply. GitHub Actions' macOS runners do not come with Docker installed, because of licensing issues: https://github.com/actions/runner-images/issues/17 Then there is the issue that the macOS runners are virtual instances, and pass-through virtualization has not been enabled: https://github.com/douglascamata/setup-docker-macos-action#:...

Bummer there's no free tier. I've been bashing my head against an intermittent CI failure problem on Github runners for probably a couple years now. I think it's related to the networking stack in their runner image and the fact that I'm using docker in docker to unit test a docker firewall. While I do appreciate that someone at Github did actually look at my issue, they totally missed the point. https://github.com/actions/runner-images/issues/11786 Are there any reasonable alternatives for a really tiny FOSS project?

May not be true anymore but was in the past when Docker first introduced the limits. Very hard to find anything definitive still left on the web. This is all I could find... https://github.com/actions/runner-images/issues/1445#issueco... https://github.com/actions/runner-images/issues/1445#issueco...