-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to GHA M1 runners #429
Comments
Wow! This is fantastic, I checked 2 months ago and it cost quite a lot. Thanks for the update. |
I don't think this is relevant to us but just in case: |
Late to the party, but happy to see GitHub finally enabled the ARM runners. That can simplify the image build pipeline |
Sadly, the runner is has some virtualization setting not support running docker inside yet https://github.com/douglascamata/setup-docker-macos-action?tab=readme-ov-file#arm64-processors-m1-m2-m3-series-used-on-macos-14-images-are-unsupported |
I am wondering, how does it work on the self-hosted runner? Is the runner running outside of Docker so it does not require nested virtualization? |
From what I understand, the different between the self-hosted runner and the github runner is the github runner is already a virtulized machine. It not supported to have another virtualization layer inside it. |
Looks like there isn't much we can do here for foreseeable future so I'll close this. |
Currently we use our own runners for the Arm build. GitHub recently made M1 runners available. Switching to them should hopefully significantly streamline our build.
I think this should be done first, and will hopefully make it easier to then remove the
artifact-upload
steps, as discussed in #414https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories
See
macos-14
runner.The text was updated successfully, but these errors were encountered: