These overlay directories are automatically committed to the build OSTree repoby coreos-assembler. They are then explicitly included in our various manifestfiles via `ostree-layers` (this used to be done automatically, but that's nolonger the case).05core------This overlay matches `fedora-coreos-base.yaml`; core Ignition+ostree bits.This overlay is shared with RHCOS/SCOS 9.08nouveau---------Blacklist the nouveau driver because it causes issues with some NVidia GPUs in EC2,and we don't have a use case for FCOS with nouveau."Cannot boot an p3.2xlarge instance with RHCOS (g3.4xlarge is working)"https://bugzilla.redhat.com/show_bug.cgi?id=170005609misc------Warning about `/etc/sysconfig`.10disk-images-------Configuration files for bootc and image-builder. These are used when buildingour disk images.15fcos------Things that are more closely "Fedora CoreOS":* disable password logins by default over SSH* enable SSH keys written by Ignition and Afterburn* branding (MOTD)* enable FCOS-specific services by default* display warnings on the console if no ignition config was provided or no sshkey found.* display warnings if mount points are not set up properly17fcos-container-signing------------------------Configuration for container signature verification for ourfedora-coreos containers pulled from quay.io. Initially addinghere in a separate overlay to make it easy to include on specificstreams for the time being. Eventually can probably put this in15fcos.20platform-chrony-----------------Add static chrony configuration for NTP servers provided on platformssuch as `azure`, `aws`, `gcp`. The chrony config for these NTP serversshould override other chrony configuration (e.g. DHCP-provided)configuration.30lvmdevices-------------------Populate an lvmdevices(8) file to limit LVM from autoactivating alldevices it sees in a system. By default systems will get a "blank"configuration file with a comment in it explaining what it is usedfor. There is also a one-time "populate" service that will run andadd any devices it sees into the devices file. This will serve toimport existing devices on upgrading systems or new systems withpre-existing LVM devices attached. See the tracker issue [1] for moreinformation.[1] https://github.com/coreos/fedora-coreos-tracker/issues/151735container-signing-migration-----------------------------This overlay will be used to perform a migration suchthat upgrading systems will start using container signaturesfor verification as opposed to OSTree commit signatures.This is a necessary step for F43 as part of the build-via-containerchange [1]. See [2].[1] https://github.com/coreos/fedora-coreos-tracker/issues/1969[2] https://github.com/coreos/fedora-coreos-tracker/issues/202940import-virtiofs-systemd-credentials-------------------------------------Support exposing systemd-credentials via virtiofs. This is across-architecture alternative way to get settings into aninstance when Ignition isn't an option (i.e. non-coreos bootablecontainer) or when we want to explicity test behavior when noIgnition is provided to an instance.