I tried many times but the extension won't install on a VM with B1ls size running Ubuntu Image..The install runs forever and shows as 'unavailable' in the Portal. Can this doc be updated if this particular size can't be used for this extension? Thanks.
ā Do not edit this section. It is required for docs.microsoft.com ā GitHub issue linking.
@jits2019 the extension does not have a VM size requirement. Likely there is a different issue.
What version of Ubuntu are you running? Have you tried it on the same image using another VM size?
I have tried with latest ubuntu and other ones too..other VM size works with same image..also other OS works on same vm size..issue is only with B1ls + Ubuntu
hmm strange.
@yyanev @SanDeo-MSFT is this expected?
Also pinging @ayshakeen in case this has come up before on B1s
We did some debugging and this is what we found:
There are too may repos registered with apt. Maybe we donāt need http://azure.archive.com/ubuntu and removing it from the image will improve the situation; I donāt know. The aadloing package is pretty small and if the script manages to finish, the AAD Login will work.
For now, the only workaround I can think of is this:
Thanks @yyanev !
@jits2019 you can go ahead and give the work arounds a try. All in all, seems to be based on limited resources of that specific series.
We won't add that info to the document at this time but you comment will remain on the doc so if other users encounter the same problem they will be able to see the work around. If we have enough users running into this issue and trying it on this size we can always reopen and consider adding it to the documentation.
Added a note that if you are installing this extension on a previously created VM it should be allocated with at least 1GB of memory for the install to succeed.
Most helpful comment
We did some debugging and this is what we found:
There are too may repos registered with apt. Maybe we donāt need http://azure.archive.com/ubuntu and removing it from the image will improve the situation; I donāt know. The aadloing package is pretty small and if the script manages to finish, the AAD Login will work.
For now, the only workaround I can think of is this: