Azure should, as far as I am aware, support Rocky on these extensions. Rocky should be listed on that page, and Iâll see what I can do to help that.
Iâm also glad that AWS has us listed, we should definitely strive to be added to the MSFT ones, as you mentioned.
Azure is willing to support Rocky on their cloud. The issue here was purely a legal one with the RESF being unable to take on certain requirements for a commercial partnership with MSFT. However, weâre still publishing the images, and Microsoft is still supporting Rocky on the platform. In short, I wouldnât worry too much about itâMicrosoft is not âanti rockyâ in any way.
Glad to hear you now have it on your list to push for Rocky to be on the extension. The issue I ran into within the last few months may be purely a training and documentation issue then. I was literally told by their support that they would refuse to assist with troubleshooting their extensions because Rocky was not on the list of supported OSs. Indeed they threatened to close a ticket unless I spun up a CentOS 8.5 VM to continue troubleshooting since that was on their supported list. It did not matter that CentOS 8.5 was no longer supported ⌠only what was on that list seemed to matter.
In any case, any assistance/pushing you can do to get Rocky Linux listed on that page is most appreciated!
Iâm really glad this is making some headway now, however I have a couple of recommendation based of our usage.
Is it possible for you to change the publisher name to something thatâs a bit more friendly? In our infra templates we have now has to replace âOpenLogicâ and âCentOSâ to âerockyenterprisesoftwarefoundationinc1653071250513â and ârockylinuxâ this doesnât look as genuine and might put off some people using these images.
Secondly, most marketplace images have multiple SKUs for each release, so OpenLogic CentOS has â8_3-gen2â, â8_4-gen2â and â8_5-gen2â which means I can be explicit when build VMs. Instead you just have a SKU named âfreeâ which doesnât make it clear what base image is being used, and if I was to build a VM 2 weeks apart, I donât actually know if the Rocky version might have changed. (Eg from 8.6 to 9.0)
To use this image, I also have to select a payment plan, which I can set to free, but most images donât need this. This means this image is not a drop in replacement for CentOS images that donât need this. Its not a deal-breaker, but it means you need to add plan information to templates as well as the image information. Iâm hoping that working with Microsoft these images will be marked as first party, avoiding this in the future.
I have created an Azure VM from Rocky a couple of times.
I tell Azure to use my usual existing ssh key.
I am unable to log in with the ssh key.
I set up to use the serial console, login with my 76 character password (kidding) and look at the SSH key, with the following command.
[eyeadmin@Rocky-8-2 ~]$ cat .ssh/authorized_keys
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCmzAqw9WsJwNqckmkVOsAq5uMA b8peb0XZsk+BfPNg+JXJtkMtpmgEC5yFek1KEVErr52W2YDUvLbtzmUxdBEZ8nC3
⌠several lines removed here âŚ
Zy81zSCEzpmVuEbA8A+Waj8JuWaEGHX+H8dESXU= generated-by-azure
[eyeadmin@Rocky-8-2 ~]$ cat /etc/rocky-release
Rocky Linux release 8.6 (Green Obsidian)
As you can see, âsomethingâ has wrapped the key over multiple lines. And added âgenerated-by-azureâ (Wha?)
Going by the first and last 20 chars or so, this is the right public key, but it wonât work this way.
I have not had this problem on other images, so it seems possible that something in the setup of the Rocky image is changing the key as it copies it to the authorized_keys file.
Yes! i apologize for the latency on this. Thanks for your patience.
Yes, absolutely. I am working through this now but it is taking some time as it requires some approvals. I will update as I have more info
Oh, that is a great point. I am new to publishing in the Azure marketplace, so I really appreciate the tips and suggestions. I will look at implementing this in the next publisher account.
That is⌠unfortunate. I will ask MSFT about this and see what we can do to resolve.
If it would help, we are also able to provide the build artifacts (VHD files) for users to upload themselves. I understand thereâs also a preview feature for Shared Compute Galleries. If we can get those setup, I believe some of this will be relieved as wellâsince the Shared CGs are outside the Marketplace completely. My understanding is this is the same/similar to making an AWS AMI âPublicâ to be consumed/copied by others.
Hi,
we have the same situation and the same issue - we are an Azure CSP and we have an ISV customer that can not get the offer in CSP. We would kindly ask you to enable the offer for CSP.
Fantastic. I was just looking at setting up two Azure VM using Rocky Linux so this is great timing. Looking forward to seeing CSP enabled and for Rocky Linux 9. Thanks for all effort and work you have done on this â much appreciated by the community!
@neil - Any updates? Hoping to deploy a few more of these into Azure, ideally on 9 now. Marketplace with CSP enabled would be nice, but the VHD for manual upload would be fantastic. Thanks!!