Open lareeth opened 9 months ago
This would be extremely useful to have working for my projects as well. Use case is to build arm64 docker images that can be deployed through Azure IoT to Jetsons and raspberry pi's. Having vmss support would ease management of the build server.
Yes please, we are really looking forward for this to be fixed!
How is this still being ignored when it's 2024 and ARM is everywhere?? We've been wanting to switch to ADO for more than 2 years now and this is the one single blocker! I expected that after all this time this would already be ready to use but every time I come back to check I am once again disappointed that it's still being ignored.
Same here; out-of-the-box support for ARM64 would be highly appreciated
+1 on this, can we please get this moving please.
Any updates on this one?
I would suggest emailing opensource@microsoft.com
with something to the effect of
Dear Microsoft Open Source,
Please can you provide some support in prioritising a feature request for Azure DevOps, this feature request provides support for VMSS pools using ARM64 architecture. This is a important feature especially with Azure's support for ARM64 based instances, and the announcement of Server 2025 supporting ARM64.
Please can you respond to the feature request:
Issue: https://github.com/microsoft/vsts-azurevm-extension/issues/230
Pull Request: https://github.com/microsoft/vsts-azurevm-extension/pull/232
Regards,
<Name>
Hi,
Can we have this fixed? We are moving our pipeline from Jenkins to AzureDevops and the current workaround to make this work is not that great.
When enable Azure DevOps to use a VMSS pool configured with an ARM64 image, the deployment fails due to the following error
The current CPU architecture is not supported. Deployment agent requires x64 architecture.
https://github.com/microsoft/vsts-azurevm-extension/blob/f1b3ace497d1413fa0aa11d4ede646053a244cda/ExtensionHandler/Linux/src/AzureRM.py#L165-L171
What's the reason for the limitation, and are there plans to support ARM64 deployments?
I have also tried replacing the image that gets passed into the deployment
But it appears the extensions throws the error before it tries to run the agent