Skip to content
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

support macos GHA runners #172

Open
Hotell opened this issue Nov 4, 2024 · 2 comments
Open

support macos GHA runners #172

Hotell opened this issue Nov 4, 2024 · 2 comments
Assignees
Labels
enhancement Feature request/improved experience

Comments

@Hotell
Copy link

Hotell commented Nov 4, 2024

We are migrating our infra to GHA where we wanna leverage most performant runners => macos ARM

Unfortunately az cli fails when using those runners.

https://github.com/microsoft/fluentui/actions/runs/11633493345/job/32398753344

Image

@Hotell Hotell added the need-to-triage Requires investigation label Nov 4, 2024
@MoChilia MoChilia added enhancement Feature request/improved experience and removed need-to-triage Requires investigation labels Nov 5, 2024
@MoChilia
Copy link
Member

MoChilia commented Nov 5, 2024

Hi @Hotell, Azure/cli is designed to use docker in the action for running Azure CLI scripts. But the docker image built by azure-cli provides a standalone Linux container, so currently MacOS is not supported, see https://learn.microsoft.com/en-us/cli/azure/run-azure-cli-docker. We are continuously exploring ways to support additional operating systems for Azure/cli.

For anyone who would like to see this feature implemented, please give a thumbs up to this issue. If it receives high demand, we will prioritize its development.

@Hotell
Copy link
Author

Hotell commented Nov 5, 2024

Thanks for quick response.

Here’s some additional context:

Your tool is currently our only compliant option for accessing Azure services within our security directives. While there is a temporary workaround using Ubuntu, it is significantly more costly and inefficient, resulting in pipelines that are 90% slower in our case. Given these constraints, we would greatly appreciate if this could be prioritized on your end.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request/improved experience
Projects
None yet
Development

No branches or pull requests

2 participants