quine-global-labs/mirror-coreos-fedora-coreos-config
1
0
Fork 0
mirror of https://github.com/coreos/fedora-coreos-config.git synced 2026-11-03 14:49:47 -09:00
Code Issues Projects Releases Packages Wiki Activity
mirror-coreos-fedora-coreos.../image-base.yaml

46 lines
1.5 KiB
YAML
Raw Permalink Normal View History

Move next-devel to cgroupsv2 for new nodes All we need to do is to make the associated karg be specific to `testing-devel` by uplisting it to `image.yaml`. Then `next-devel` will naturally shed it when `image-base.yaml` gets synced over. See: https://github.com/coreos/fedora-coreos-tracker/issues/292
2021-03-26 07:12:58 -08:00
# This file is shared by all streams. For a stream-specific change, use
# image.yaml instead.
image.yaml: split out image-base.yaml The `image.yaml` file will be unique to each stream (like `manifest.yaml`), while `image-base.yaml` will be shared by all streams (like `manifests/fedora-coreos-base.yaml`). Prep for dropping the `systemd.unified_cgroup_hierarchy=0` karg on the next stream.
2021-03-24 13:48:10 -08:00
# Target disk size in GB.
# Make it at least 10G because we want the rootfs to be at least 8G:
# https://github.com/coreos/fedora-coreos-tracker/issues/586
size: 10
drop image-default.yaml; migrate settings to image-base.yaml There wasn't much point in have two levels of indirection here. Let's merge everything into one file.
2026-01-20 10:36:36 -09:00
# Additional default kernel arguments injected into disk images
image.yaml: split out image-base.yaml The `image.yaml` file will be unique to each stream (like `manifest.yaml`), while `image-base.yaml` will be shared by all streams (like `manifests/fedora-coreos-base.yaml`). Prep for dropping the `systemd.unified_cgroup_hierarchy=0` karg on the next stream.
2021-03-24 13:48:10 -08:00
extra-kargs:
# Disable SMT on systems vulnerable to MDS or any similar future issue.
- mitigations=auto,nosmt
drop image-default.yaml; migrate settings to image-base.yaml There wasn't much point in have two levels of indirection here. Let's merge everything into one file.
2026-01-20 10:36:36 -09:00
# VMware OVA settings.
## VMware hardware versions: https://kb.vmware.com/s/article/1003746
## We use the newest version allowed by the oldest non-EOL VMware
## Workstation/Player/Fusion/ESXi release: https://lifecycle.vmware.com/
image-base: bump VMware hardware version to 17 The last VMware products requiring older hardware versions are now EOL. Fixes https://github.com/coreos/fedora-coreos-tracker/issues/1141.
2022-10-17 07:43:06 -08:00
vmware-hw-version: 17
drop image-default.yaml; migrate settings to image-base.yaml There wasn't much point in have two levels of indirection here. Let's merge everything into one file.
2026-01-20 10:36:36 -09:00
## Identify as Fedora 64 bit Guest
vmware-os-type: fedora64Guest
## Enable SecureBoot by default
vmware-secure-boot: true
# AWS AMI Settings.
aws-imdsv2-only: true
aws-volume-type: "gp3"
aws-x86-boot-mode: "uefi-preferred"
image-base.yaml: set `compressor: xz` This will be picked up by `cosa compress` to know to compress with xz.
2022-11-21 13:39:09 -09:00
compressor: xz
image-base.yaml: compress applehv with gzip, hyperv with zip These platforms are already compressed using those compressors today, but we're moving that policy out of cosa and into here since it's not a requirement from the platform itself and more an opinion (which others may want to differ from). This uses a new `platform-compressor` key which `cosa compress` will learn to read.
2024-12-03 08:15:32 -09:00
platform-compressor:
# On Windows, it's the only compression tool we can rely on.
hyperv: zip
# On macOS, it's the only compression tool we can rely on.
applehv: gzip
image-base: specify gzip platform compressor for DigitalOcean When we build DigitalOcean using osbuild this will be the part that tells the later `cosa compress` stage to compress the qcow2 using gzip rather than xz.
2025-02-13 11:57:36 -09:00
# For DigitalOcean you can upload a qcow2 compressed in either gzip or bzip2
# https://docs.digitalocean.com/products/custom-images/how-to/upload/
digitalocean: gzip
image.yaml: switch to EROFS; deploying via container These changes are ones that we are adopting for F42+ and since F42 GA is a GO for Tuesday 04/15 we'll go ahead and make the change for `testing-devel` now. We can update image-base.yaml because now the change can apply everywhere. - https://github.com/coreos/fedora-coreos-tracker/issues/1823 - https://github.com/coreos/fedora-coreos-tracker/issues/1852
2025-04-11 08:02:19 -08:00
image-base,image-default: drop references to deploy-via-container This is no longer used. See also [1] [2]. [1] https://github.com/coreos/coreos-assembler/commit/43b99d51a7bf201575699e603ed9214d43b9f4a0 [2] https://github.com/coreos/coreos-assembler/commit/a876a9b592c375d64c33277f23c8d4a3efa412ac
2025-07-29 08:59:51 -08:00
# Set container-imgref
promote container signature verification and migration to it This has rolled out on the `next` stream. Let's now promote it to our other streams and let the normal promotion progress (i.e. testing-devel -> testing -> stable) take place. Part of https://github.com/coreos/fedora-coreos-tracker/issues/2029
2025-09-19 13:04:00 -08:00
container-imgref: "ostree-image-signed:docker://quay.io/fedora/fedora-coreos:{stream}"
image.yaml: switch to EROFS; deploying via container These changes are ones that we are adopting for F42+ and since F42 GA is a GO for Tuesday 04/15 we'll go ahead and make the change for `testing-devel` now. We can update image-base.yaml because now the change can apply everywhere. - https://github.com/coreos/fedora-coreos-tracker/issues/1823 - https://github.com/coreos/fedora-coreos-tracker/issues/1852
2025-04-11 08:02:19 -08:00
# Enable 'erofs' by default for the rootfs in the Live ISO/PXE artifacts
live-rootfs-fstype: "erofs"
image-base: use -Efragments for erofs creation As suggested by the maintainer we'll change this option from `-Eall-fragments,fragdedupe=inode` to -Efragments. Closes https://github.com/coreos/fedora-coreos-tracker/issues/1991
2025-11-12 05:02:35 -09:00
live-rootfs-fsoptions: "-zlzma,level=6 -Efragments -C1048576 --quiet"
Reference in a new issue Copy permalink