Copy the latest multi-arch lockfiles and overrides from next-devel at f91914d6. Update the F45 bootc builder image while preserving the testing-devel stream identity.
see coreos/coreos-assembler#3607
With the above PR, cosa's image-default.yaml adds 3 configuration
fields. The defaults provided differ from before. Overide the new
configuration fields to maintain old defaults.
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
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.
Right now, our images are triggering the new 8G warning because the disk
size itself is 8G, so the rootfs is less than that. Let's go to 10G so
we meet our own standard.
We have all the piece in place now to move to conditional networking. So
let's drop the `rd.neednet=1` firstboot karg.
Also don't enable coreos-liveiso-network-kargs.service on FCOS since
it's no longer needed (i.e. the live ISO will now enable initrd
networking as required given the embedded Ignition config).
On RHCOS, we still need it for now until we move to spec3. Then we can
remove the service and script completely.
Fixes: https://github.com/coreos/fedora-coreos-tracker/issues/443
This removes the hardcoded `ip=dhcp,dhcp6` from bootloader configuration.
The default value has been moved to Afterburn (>= 4.4.0), making
this dynamically injected at runtime. On some platforms (e.g. VMware),
this also allows user-controlled overriding.
This updates `image` manifest to capture current firstboot kernel
arguments. Those are effectively the same parameters used by GRUB
and overridable by coreos-installer, which so far have been
hardcoded inside `grub.cfg`.
FCOS is likely to ship with CGroupsV1 to start, since most of the
containerization ecosystem isn't yet ready for V2.
Pass the `systemd.unified_cgroup_hierarchy=0` karg to enable this. This
should at least allow podman Kola tests to pass.
For more information, see:
https://github.com/coreos/fedora-coreos-tracker/issues/292
This should really be done in rpm-ostree if `machineid-compat: false`:
https://github.com/projectatomic/rpm-ostree/issues/1803
But for now let's do the quick hack here.
The core problem is today the RPM scriptlets are enabling units,
but for us Ignition+presets should be the canonical definition of
things.
This avoids having another source of truth.
Let's just support configuring the base disk size for now so that we
say we *do* have some configuration. We need to abstract this for
multiple reasons (we want to remove Anaconda, and even without removing
Anaconda we want to do dual bios/UEFI and also potentially arch-specific
code).
Most people will probably be OK for now configuring the base ostree and the
outer image size.
This commit doesn't yet remove image.ks in order to support version skew,
but we intend to shortly drop it.
