Skip to content

Support for VMs on Apple M1 #2187

Closed
Closed

Description

@pmatos

Is there any plan to release VMs in Apple M1 hardware to run GitHub Actions?

Activity

  1. thejoebourneidentity commented on Dec 2, 2020

    @thejoebourneidentity

    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!

  2. tomiiide commented on Jan 25, 2021

    @tomiiide

    @thejoebourneidentity Any update on this yet?

  3. paulocoutinhox commented on Feb 13, 2021

    @paulocoutinhox
  4. QuiiBz commented on Feb 14, 2021

    @QuiiBz

    AWS Now Offer It:
    https://9to5mac.com/2021/02/02/m1-mac-mini-in-the-cloud/

    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.

  5. ioquatix commented on Mar 4, 2021

    @ioquatix

    Has anyone tried the self-hosted runner on a local M1?

  6. lloeki commented on Mar 4, 2021

    @lloeki

    @ioquatix yes I have. It works but it's quite annoying in the current state of GHA:

    • The runner process itself runs under Rosetta because at some point it hinges on Intel binaries.
    • I have overriden Rosetta 2 by using arch(1) on each run step: 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)
    • The GHA UI only allows one to pick from a very limited list†, and thus I created it as macOS x86_64, which automatically adds unremovable tags macOS and x86_64 on 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 the arch commands above.
    • I added a manual arm64 tag to distinguish it.
    • It is only possible to add a runner to one GH project or one GH organisation, and with the current implementation you can really only have one runner per user on a machine††. This is fairly limiting.
    • Since the runner lives as a process under a regular user (which I created one specifically for), unless you take extra measures (at the -very- least chmod 700 all 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.

  7. lloeki commented on Mar 4, 2021

    @lloeki

    @ioquatix that's basically what I used (just follow the registering steps of macOS x64 provided by GHA's UI):

    name: Build
    on:
        - push
    
    jobs:
      try-macos-arm64:
        name: Try macOS on M1
        runs-on: [self-hosted, macOS, ARM64]
        defaults:
          run:
            shell: "/usr/bin/arch -arch arm64e /bin/bash {0}"
        steps:
            - name: Status
              run: |
                clang --version
                uname -a
            - name: Checkout
              uses: actions/checkout@v2
            - name: Set Ruby metadata
              id: ruby
              run: |
                  ruby -e 'puts RUBY_PLATFORM' | tee ruby_platform
                  echo "::set-output name=RUBY_PLATFORM::$(cat ruby_platform)"
                  ruby -e 'puts Gem.platforms.last.to_s' | tee gem_platform
                  echo "::set-output name=GEM_PLATFORM::$(cat gem_platform)"

    (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)

  8. maxim-lobanov commented on Mar 4, 2021

    @maxim-lobanov
    Contributor

    Related issue: actions/runner#805

  9. lloeki commented on Mar 4, 2021

    @lloeki

    @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.

  10. 87 remaining items

  11. Siedlerchr commented on Mar 1, 2023

    @Siedlerchr

    In the roadmap moved to Q4/2023... So either end of year or at some undefined point in the future...

  12. fkorotkov commented on Mar 19, 2023

    @fkorotkov

    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.

  13. diogot commented on Mar 20, 2023

    @diogot

    We give up, just bought a Mac mini M2 and going self hosted.

  14. sammcj commented on Apr 9, 2023

    @sammcj

    Any update on this? All new macs are Apple Silicon, x86 is pretty much dead.

  15. tarcieri commented on Apr 10, 2023

    @tarcieri
  16. gillbates commented on Apr 22, 2023

    @gillbates

    anyone knows how it goes now?

  17. jpmckinney commented on Apr 22, 2023

    @jpmckinney

    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.

  18. locked as spam and limited conversation to collaborators on Apr 27, 2023
  19. unlocked this conversation on Apr 27, 2023
  20. locked as off topic and limited conversation to collaborators on Apr 27, 2023
  21. mikhailkoliada commented on Oct 2, 2023

    @mikhailkoliada
    Contributor

    Adrressed as #8439 and M1 is now available!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions