GitHub Linux ARM64 hosted runners now available for free in public repositories

181 点作者 Aissen4 个月前

14 条评论

This is excellent news, as it should unblock having precompiled packages available for a number of applications for arm64—for me, most notably, OpenZFS: <a href="https://github.com/openzfs/zfs/issues/14511">https://github.com/openzfs/zfs/issues/14511</a>

评论 #42729239 未加载

ecnahc5154 个月前

While this is great, for people claiming they can now built multi-arch images without emulation, how are you planning on doing so? As far as I know, if you want to build multi-arch images on native runners for each platform, you basically need to:* Configure a workflow with 1 job for each arch, each building a standalone single-arch image, tagging it with a unique tag, and pushing each to your registry* Configure another job which runs at the completion of the previous jobs that creates a combined manifest containing each image using `docker manifest create`.Basically, doing the steps listed in <a href="https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/" rel="nofollow">https://www.docker.com/blog/multi-arch-build-and-images-the-...</a> under "The hard way with docker manifest ".Does anyone have a better approach, or some reusable workflows/GHA that make this process simpler? I know about Depot.dev which basically abstracts the runners away and handles all of this for you, but I don't see a good way to do this yourself without GitHub offering some better abstraction for building docker images.Edit: I just noticed <a href="https://news.ycombinator.com/item?id=42729529">https://news.ycombinator.com/item?id=42729529</a> which has a great example of exactly these steps (and I just realized you can just push the digests, instead of tags too, which is nice).

评论 #42734320 未加载

agartner4 个月前

Here's a quick example I put together on how to use these runners to accelerate docker builds: <a href="https://github.com/gartnera/actions-arm64-native-example">https://github.com/gartnera/actions-arm64-native-example</a>

评论 #42729720 未加载

kylegalbraith4 个月前

This is exciting to see as arm64 is really a growing space, as we've seen since first launching our Docker image build acceleration [0]. Free for public repos is definitely a strong pull if you can live with some of the quirks.Even with this, building multi-platform Docker images with fast persistent caching in GitHub Actions will still be slow in the worst case and tedious in the best case.We've also expanded into GitHub Actions runners, bringing our fast caching and faster compute into the actual runner.We've done some cool things like making caching and disk access faster using ramdisks, Ceph, and blob storage [1]. We're offering Intel, ARM, and macOS runners at half the cost of what GitHub offers to private repos. We're also focused on accelerating even more builds outside of the runner. [2][0] <a href="https://depot.dev/products/container-builds">https://depot.dev/products/container-builds</a>[1] <a href="https://depot.dev/blog/introducing-github-actions-ultra-runners">https://depot.dev/blog/introducing-github-actions-ultra-runn...</a>[2] <a href="https://depot.dev/blog/introducing-depot-cache">https://depot.dev/blog/introducing-depot-cache</a>

评论 #42731182 未加载

mystified50164 个月前

Our CI runners live on a box in the corner of the office and their only operating cost is my time.Paying someone for CI compute seems insane. The load is so variable that you never know if your monthly bill will be zero or several hundred/thousand dollars. I especially don't want my employees to consider that each and every push costs the company a nonzero amount of money. CI should be totally free and unrestricted. If a new employee has a really bad day and fires off a hundred CI runs (as we all have), I don't want to explain to accounting why there's an enormous spike in the bill.It costs us a couple of my salaried hours a month to maintain our on-site infra. Far, far less than our present AWS bill. Most months it needs no attention. It just sits there and does its job. Hell, it's even solar powered.

评论 #42731113 未加载

评论 #42737286 未加载

0xcoffee4 个月前

Is the price cheaper than x64 instances?For 'large' instances, ARM64 is cheaper: <a href="https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates-for-arm64-powered-larger-runners" rel="nofollow">https://docs.github.com/en/billing/managing-billing-for-your...</a>So what about regular instances?

bhollis4 个月前

We're using Go, so cross-compilation has never been a big problem (for producing artifacts). But this'll be great for testing on ARM. I'm interested to see the performance of these instances too - our experience has been that Amazon's Graviton processors have fantastic bang-for-buck vs. Intel/AMD.

评论 #42731879 未加载

评论 #42730291 未加载

CaliforniaKarl4 个月前

This is awesome!!!I switched from an Intel Mac to an Apple Silicon Mac a few months ago, and have been trying to do as much stuff as possible on ARM.One thing this should do, is make people think more about switching their cloud-based workflows to ARM CPUs, which are generally less expensive.

amacneil4 个月前

For private repos, Github runners are slow and overpriced. We switched to buildjet.com runners and have no regrets.

评论 #42730136 未加载

verdverm4 个月前

This is awesome, I have been dealing with weird errors in GHA for years when having to emulate for multi arch builds

mlhpdx4 个月前

Nice. I had gone looking for this a week or two ago and was surprised it wasn’t available to me.

suryao4 个月前

For cheaper (for private repos) and faster arm64 runners, check out what we're making at WarpBuild.We also support spinning up self-hosted runners on your AWS/gcp/azure in just a couple of clicks.

评论 #42734400 未加载

评论 #42730251 未加载

tonymet4 个月前

this makes distributing Raspberry Pi binaries a bit easier .I was running the Github actions runner on my raspi (which works petty well)

joshstrange4 个月前

GitHub Actions is overpriced and slow. WarpBuild [0] is so much nicer. Our iOS build times dropped in half and cost less than the base macOS runner on GHA. It couldn’t have been easier, just set it up, changed the runner image name, and then I promptly forgot about it because it works the exact same way as before. GH secrets work, runs show up in the same place. It’s one of the only times I’ve improved performance and saved money all without changing anything on my end.I did have to move my repos into an organization because you can only use WarpBuild with organizations, not personal accounts, but I probably should have been doing that anyway.[0] <a href="https://www.warpbuild.com">https://www.warpbuild.com</a>