I find after launching a cloud image built from the official Fedora cloud images, I need to do a lot of package updates after installation.
Are these images ever updated with the latest packages within the current major version, or do they always stay the same until the next major version?
With almost all images, they are built at release time and never updated. It is left to the user to perform updates after the initial installation.
I do not use cloud images so have no first hand experience, but it is that way with all other release spin ISOs I see and have used from the download site.
There are some relatively current updated spins available at Index of /pub/alt/live-respins but I see no cloud images there.
Thanks, I feel this is an area where Fedora can improve, the latest Ubuntu 22.04 cloud image is from 22 August, from an initial release date of 25 April.
Not only does this speed up deployment of new instances, it also reduces the burden on mirrors.
The images available for download from fedoraproject.org remain the same for a release.
We do upload nightly Fedora cloud images to both Azure and AWS, but they aren’t currently immediately promoted to be the default so you have to know where to find them to boot them.
For Azure, I currently manually promote an image to be the default every ~2 weeks. I’d like to get testing on them automated so we can roll out fresh images regularly without much human intervention, but I’m not sure when I’ll get that done.
I use Oracle Cloud which has no native Fedora images, just Alma, Rocky and CentOS, so it is necessary for me to import a cloud image for Fedora and use that. The number of packages I have to pull in straight after first boot runs into the hundreds, and will grow until I shift to version 41 when it releases.
There was brief talk of updating the cloud images more frequently here, but unfortunately it didn’t seem to go anywhere.
We build Cloud images nightly. You can find the nightly composes at Index of /compose/cloud and import a recent image from one.
Thanks for the pointer. Is there a reason why none of these subsequent releases are ever published to the main cloud download page? Wouldn’t it just be as simple as publishing a generic link to a file which is symlinked to the latest snapshot?
Related 3 year old discussion:
So apparently the cloud image download page isn’t updated because some people aren’t satisfied with the amount of QA that can be automatically applied to them.
That’s a shame. Ubuntu’s Cloud images are never more than a few days old and unlike Fedora’s koji images they even have gpg-signed sha256sums: link
Initial package updates are very quick as a result and this reduces the load on mirrors. I feel this is an area Fedora could improve on.
the nightlies have checksums. https://kojipkgs.fedoraproject.org/compose/cloud/Fedora-Cloud-41-20241216.0/compose/Cloud/x86_64/images/Fedora-Cloud-41-20241216.0-x86_64-CHECKSUM
True, but I like the added assurance of pgp-signed checksums, like the “main” cloud images have: https://fedora.mirrorservice.org/fedora/linux/releases/41/Cloud/aarch64/images/Fedora-Cloud-41-1.4-aarch64-CHECKSUM
oh, huh, I don’t know why the difference off the top of my head.
Hi @adamwill
Sorry, I’m not sure where to report it, but I’ve found that the symlink to latest-Fedora-Cloud-41 has disappeared. It’s there for 40, just not 41. Hopefully it’s not too much trouble to restore.
Cheers!
Hi @skyblaster , there is a recent bug report for this:
https://pagure.io/releng/issue/12521