Search results

* Identify opportunities to share base images * We will start building official base Fedora bootable container images.

...Fedora Trademarks to label media made from exact copies of the CD and DVD images distributed by the Fedora Project and its mirrors. The guidelines relating ==== Virtual images or appliances with unmodified Fedora software ====

= aarch64 SBC (Single Board Computer) Disk Images = We will deliver the first supported SBC disk images for aarch64.

| <!-- subtask -->every two weeks, scan for images which pass all tests * If we get to the point of only building images when there are changes to the content set, that process still needs to noti

= Default podman created images to zstd:chunked = Modify podman push to default to creating images with zstd:chunked, allowing users to modify containers.conf to continue to

= ZRAM support for ARM images <!-- The name of your change proposal --> = Enable ZRAM for swap on ARMv7 and aarch64 pre generated images to improve performance and reliability on ARM Single Board Computers such a

= Register EC2 Cloud Images with uefi-preferred AMI flag = This proposal is to register the Fedora EC2 images with `uefi-preferred`, having the effect of switching to booting in UEFI mo

...designed to give the end users a simple workflow to build their own custom images. The aim of this change is to create an additional, non-blocking Fedora Wor ...s://docs.pagure.org/pungi/configuration.html#osbuild-composer-for-building-images pungi] and [https://github.com/osbuild/koji-osbuild/ koji] documentation).

= Build Fedora Cloud Edition Images Using Kiwi in Koji = ...ImageFactory] tooling that is currently being used to build the cloud base images.

* Drop: Spins/armhfp/images/Fedora-Xfce-armhfp-_RELEASE_MILESTONE_-sda.raw.xz * Add: Workstation/aarch64/images/Fedora-Workstation-aarch64-_RELEASE_MILESTONE_-sda.raw.xz

Currenly fedming tool creates and uploads the AMI images to AWS, in all the regions. It only tests the output /usr/bin/true command ...ts of the test and if all the tests passes then then fedimg would copy the images to other regions as well.

* F23 atomic images won't be on the regular mirrors 2. Updated Fedora Atomic Host images produced every two weeks, and presented at https://getfedora.org/en/cloud/d

= No More i686 Kernels or bootable images<!-- The name of your change proposal --> = ...of everything else. No kernel means we would stop producing i686 bootable images as well.

= Cloud-base and Container images for s390x = ...widely used Fedora variants. This includes container images and Cloud-base images (qcow2 and raw format).

...t/acarter-fedora-docker-atomic-tooling/backlog?tags=livemedia,f25 ARM Disk Images, aarch64 and PXE2Live are created using LMC] - F27 .../acarter-fedora-docker-atomic-tooling/us/703 add index.asc files for cloud images for virt-builder] - F27

Fedora Media Writer will gain the ability to write ARM images to SD cards and other portable media. ...one of the primary architectures of Fedora, we should support writing the images to bootable media for devices with this architecture.

...res. This would NOT currently include other components such as Workstation images/installs, any of the various spins, or Fedora Atomic components. This would NOT currently include other components such as Workstation images/installs, any of the various spins, or Fedora Atomic components.

sen enables you to manage your containers and images interactively directly from command line. Interface is similar to [https:// * it can interactively manage your containers and images:

...images in fedora. While additional changes are being made in LMC for disk images and pxe2live, we will focus on getting support for livecds in place as our ...ch tool made it. Support for livecds will land first with support for disk images and pxe2live following and pending some upstream changes.

= Fedora Images on Azure = * Get Azure images built via the existing Pungi processes