-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add self-hosted macOS runner support? #24
Comments
@mrmachine So if I understand correctly, you do have Docker installed in your macos self-hosted runner? |
I run a GitHub self hosted runner in a container with docker desktop for Mac. |
Why would it detect it as macos then if it is already in Linux container. @crazy-max Anyway, I think we can allow this if |
Actually, sorry, it's been a while since I submitted this ticket. I think I am NOW running GitHub Actions inside a container. However, I was wanting to run the GitHub Actions runner natively (per their recommended installation instructions). Since As I said, ARM builds on hosted GitHub Actions runners are insanely slow. And the only option (I have found) for cloud based self hosted runners is to use an AWS t4g instance which is an unnecessary expense when I have an ARM based Mac that can run Docker and good bandwidth at home. |
@mrmachine I've removed os limitation (#30). Can you try with |
Behaviour
Docker Desktop works on macOS (Docker runs in a Linux VM managed by Docker Desktop).
GitHub Actions docs say only Linux runners are supported for Docker builds.
Multi-arch builds on GitHub hosted runners via
setup-qemu-action
are INSANELY slow (from 10 minutes to 1.5 hours). The same multi-arch builds on my Intel MacBook Pro with Docker Desktop is very fast.It would be great if I could utilise my own hardware to build multi-arch images quickly with GitHub Actions.
Steps to reproduce this issue
Send a job using
setup-qemu-action
to a self hosted macOS runner.Expected behaviour
setup-qemu-action
should work on self hosted macOS runners.Actual behaviour
When I attempt a build on a self-hosted macOS runner I get this error:
Configuration
Logs
The text was updated successfully, but these errors were encountered: