Open dustymabe opened 5 years ago
I think this involves the following:
Generation 2 VMs are in public preview. Among other things, they boot via UEFI. The generation is a property of the image, not the disk; the typical approach is apparently to create two linked images (for each of gens 1 and 2) backed by the same disk. That approach would require https://github.com/coreos/coreos-assembler/issues/334.
We just added Azure images to be output by our build pipeline. We are not uploading to Azure yet, but a user can workaround by uploading the image to their account directly.
Great! I'll try it out today :-)
Looks good. It seems as if the VM needs one (sometimes a few) reboot before it gets Azure DNS servers in /etc/resolv.conf. Don't know where that comes from.
how can we push this forward?
assuming you're talking about uploading directly to Azure:
Our hands are tied right now. We need a legal agreement and then accounts created. It's being worked on in the background.
Hi. Any news about that? Will FCOS ever get on the Azure Marketplace?
Azure is the only major Cloud Provider of the "big three" not having FCOS in the Marketplace that's embarassing.
No update.
@dustymabe : Just me regular question: any updates about that ?
The situation is still as described in https://github.com/coreos/fedora-coreos-tracker/issues/148#issuecomment-625006126. Locking the issue to reduce noise.
It appears Azure now has a community gallery (preview) that we should be able to use to share images that we create publicly.
This is part of https://github.com/coreos/fedora-coreos-tracker/issues/146 and tracks the work/discussion around uploading to Azure.