Microsoft publishes a publically-available linux distribution not labelled "internal" by 2025.
As of 2022, Microsoft has a distro named Mariner, but it is for labelled as for internal use: https://www.tomshardware.com/news/microsoft-released-cbl-mariner-linux-distro
1,000🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ484 | |
| 2 | Ṁ91 | |
| 3 | Ṁ38 | |
| 4 | Ṁ31 | |
| 5 | Ṁ28 |
People are also trading
CBL-mariner has been rebranded into Azure Linux. The official Github page still calls it "internal", but it is also prominently advertised on the Azure landing page for Linux as something for the customers to run:
The extended documentation even explicitly states:
You can deploy Azure Linux node pools in a new cluster, add Azure Linux node pools to your existing clusters, or migrate your existing nodes to Azure Linux nodes.
Considering that they explicitly advertise this as something the Azure customers can run, it is not for internal use only anymore.
@Paul I believe this should be sufficient for a "YES" resolution?
@Paul The official GitHub page for Azure Linux still unambiguously reads "internal Linux distribution". the resolution criteria clearly states "not labelled "internal".
@Paul I unresolved it. You can now re-resolve it how you see fit. (In the event that you are not 100% convinced, you may choose to allow your participants to weigh in with any other evidence before you do so.)
Already released! https://www.tomshardware.com/news/microsoft-released-cbl-mariner-linux-distro with ongoing development and ISOs available for install at https://github.com/microsoft/CBL-Mariner
@jbeshir It's labelled "internal". This market will resolve yes if they remove the "internal" designation.
@Paul Would be worth editing in a note for that, then, since it being labeled as being motivated for internal use, and it being publicly available, are different questions with different resolutions in this case.
