Closed
Description
Is there any plan to release VMs in Apple M1 hardware to run GitHub Actions?
Reacted by airsquared, silverwind, Ewout ter Hoeven, Noritada Kobayashi, Oleksandr Anyshchenko, Paul Zabelin, Xiangsong Zeng (Hsiang), Mattias Ljungström, Corey Farwell, Mike Hardy and 911 more
Reacted by berlin4apk, Dmitrii Rashchenko, Jason Leo, Kevin Su, Jules Ivanic, Jakub Kozłowski, Oliver Weiler, sensuikan1973, hussa0, Gal Ben David and 67 more
Reacted by Noah Williams, Jenny Li, Mike, Johan Steenhoven, Sukant Hajra, Stephan Müller, Stephen Belanger, Victor Khaustov, Vignesh Kothapalli, Ismail Sahin and 43 more
Activity
thejoebourneidentity commentedon Dec 2, 2020
Hi @pmatos, at this moment we do not have a ETA for enabling M1 support in the GitHub Actions hosted runners, but we are actively evaluating the feasibility of this and will provide updates on our roadmap when we have something to share!
tomiiide commentedon Jan 25, 2021
@thejoebourneidentity Any update on this yet?
paulocoutinhox commentedon Feb 13, 2021
AWS Now Offer It:
https://9to5mac.com/2021/02/02/m1-mac-mini-in-the-cloud/
QuiiBz commentedon Feb 14, 2021
It’s Scaleway who provides M1 Macs Mini, AWS doesn’t have M1 yet - only Intel. On the other hand, I believe that AWS will have M1 in a near future.
ioquatix commentedon Mar 4, 2021
Has anyone tried the self-hosted runner on a local M1?
lloeki commentedon Mar 4, 2021
@ioquatix yes I have. It works but it's quite annoying in the current state of GHA:
arch(1)on eachrunstep:arch -arch arm64 my command. It's very manual but it works perfectly to drop back into non-Rosetta land.Unfortunately without writing a full-blown custom action, GHA only allows a limited number of shells (I wish it would be possible to override the shell -command- altogether, not just the shell program from a fixed list)macOS x86_64, which automatically adds unremovable tagsmacOSandx86_64on the runner. It is kind of true since there's Rosetta available but it may not be what you want, as if you have other custom macOS runners on Intel it may still pick up non-arm64 jobs, but you may want to keep it free of this for resource management purposes, as well as not complicating the steps with more conditionals on thearchcommands above.arm64tag to distinguish it.chmod 700all other users home dirs) the runner has trivial access to everything on the machine, as well as LAN access†††. This concern is mentioned by GH when adding a new runner under the synthetic warning of "don't use custom runners on public projects". This concern would be largely solved if macOS were virtualisable on ARM as it is on Intel, but currently comes short of any VM solution to achieve that. That, or dedicate the machine to be a pure GH runner that never runs for private projects, and put it in a DMZ.† Why they don't allow a blank "custom" platform (at the cost of being on your own) is beyond me.
†† I suppose one could hack the thing to allow more but the runner CLI does not make that easy out of the box.
††† That's ultimately why I shut it down as it's on my home LAN and contains personal data on a separate account.
lloeki commentedon Mar 4, 2021
@ioquatix that's basically what I used (just follow the registering steps of macOS x64 provided by GHA's UI):
(A note for Ruby users, please do yourself a favour and install a Ruby >= 2.7.2, as Apple's Ruby 2.6 seems to miss some important stuff)
maxim-lobanov commentedon Mar 4, 2021
Related issue: actions/runner#805
lloeki commentedon Mar 4, 2021
@QuiiBz There's MacStadium as well: https://www.macstadium.com/configure?p=minig5&c=VGS2
Anyway even if there were M1 machines on AWS the cost is absolutely ludicrous. I don't see anyone using that unless they're heavily invested (a.k.a trapped with no other option) in AWS as a management platform and need it at a huge enough scale to offset the cost.
87 remaining items
Siedlerchr commentedon Mar 1, 2023
In the roadmap moved to Q4/2023... So either end of year or at some undefined point in the future...
Disable M1 build in Github Actions
Disable M1 build in Github Actions
Disable M1 build in Github Actions (#2)
fkorotkov commentedon Mar 19, 2023
Hey @naikrovek, one of Tart’s developers here. Just want to elaborate a bit about your concerns on pricing.
Tart itself is free to use on personal workstations and until your organization reaches a certain number of server installations that utilize more than 100 CPU cores combined (running Tart on 12th M1 Mac Minis for your CI is free, for example). And even after reaching the limit, our pricing is very competitive and in our assessment it’s still several times cheaper than AWS or Azure like you mentioned.
We also have a managed service where for $150 a month you can get an M1 powered GitHub Action Runner with no limit on minutes used each month. This pricing is also the best out there. For comparison, $150 is equal to 32 hours of CI workflows on Intel runners.
diogot commentedon Mar 20, 2023
We give up, just bought a Mac mini M2 and going self hosted.
sammcj commentedon Apr 9, 2023
Any update on this? All new macs are Apple Silicon, x86 is pretty much dead.
tarcieri commentedon Apr 10, 2023
From February 2023
gillbates commentedon Apr 22, 2023
anyone knows how it goes now?
jpmckinney commentedon Apr 22, 2023
Can the maintainers lock or limit interaction on this issue? It’s just people asking the same question over and over (these comments are being downvoted and deleted). Maybe create and link to a discussion where people can do that, if necessary. I’m subscribed to know when this issue is updated - not to hear folks whine.
mikhailkoliada commentedon Oct 2, 2023
Adrressed as #8439 and M1 is now available!