-
Notifications
You must be signed in to change notification settings - Fork 1k
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
macOS self-hosted runner is stuck at Authentication #1055
Comments
Dotnet core doesn't support this yet. |
Thanks for answering me @TingluoHuang!
I understand the sentence from the above link as it is supported if it had Rosetta 2, emulator. That is why, when the command worked, I expected it to run. Can we maybe indicate it on the supported devices page of the Github Actions? Also when should we expect this to land? After Dotnet 6.0 comes and after the Runner is updated? |
@salihgueler do you want to create a PR to the runner repo to include that? |
EDIT: Now I understand what you mean. I can create a PR to add it. I thought about Dotnet Core implementation, that is something I can't do but I misunderstood you, my bad. :) @TingluoHuang If I was knowledgeable enough about this topic, I would love to do it. If you people can guide me a bit, I would be more than happy to help you people out :) |
I am going to close this since this is not supported and we updated the doc. 😢 |
Describe the bug
When I try to add a self-hosted runner to macOS Big Sur on an M1 Mac Mini with Rosetta 2 installed, it gets stuck at the Authentication phase.
First I thought maybe it was because of this issue #805, but Rosetta makes it possible to run the scripts from Big Sur and M1 machines.
To Reproduce
Steps to reproduce the behavior:
The configuration is stuck at Authentication.
Expected behavior
The GitHub Actions runner configuration should successfully connects to GitHub and carries on with configuration for the runner.
Runner Version and Platform
Runner Version: v.2.277.1/v.2.278.0/v.2.277.0
macOS Big Sur on an M1 Mac Mini
What's not working?
The GitHub Actions configuration is stuck at the Authentication phase.
Job Log Output
N/A
Runner and Worker's Diagnostic Logs
Additional Information
When I try to ping
https://pipelines.actions.githubusercontent.com/oOuoF9JDrwt4sWFL9840xlBX7BV7JcSt3Zeeg4i5RRu4TRFkHD/_apis/connectionData?connectOptions=1&lastChangeId=-1&lastChangeId64=-1
with curl, it works fine.The text was updated successfully, but these errors were encountered: