This is a tracking bug for Change: Distributing Kickstart Files as OCI Artifacts For more details, see: https://fedoraproject.org/wiki/Changes/KickstartOciArtifacts Fedora distributed as bootable container ships via OCI registry. Installation is typically done by conversion into a VM image or ISO installer via osbuild (image builder), however, booting from network is a useful workflow for bare-metal fleet deployments. Required files to perform such installation are not available in the OCI repository that could be fetched from registry in a similar manner as the bootable container. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Hi Lukas, how goes this change for F42? The testable deadline is coming up in about two weeks, on Feb 4th, and changes need to be in good shape at this point https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones for Beta. Please let me know if you need to defer this to F43, otherwise if youre good to go for the change to be ready to meet the testable requirements, please update the status of the tracker bug to MODIFIED. Thanks! Aoife
Oh, I forgot to update the BZ, Aoife. It is done, the repo is available here: https://quay.io/repository/fedora/kickstart-artifacts?tab=tags&tag=latest It updates on a weekly basis. To test this: dnf install oras oras pull quay.io/fedora/kickstart-artifacts:41-amd64 I am wondering, do you know if there is a calendar I can add that has all future fedora releases? I was able to find calendars per release: https://fedorapeople.org/groups/schedule/ Thanks.