systemd/mkosi.conf.d/10-centos/mkosi.conf

# SPDX-License-Identifier: LGPL-2.1-or-later

[Match]
Distribution=centos

[Distribution]
Release=10

[Content]
Environment=
        # CentOS doesn't support btrfs so we have to use something else. We'd prefer to use XFS here but it
        # fails to mount on duplicate filesystem UUIDs which happens when running tests in parallel so we use
        # ext4 instead.
        SYSTEMD_REPART_OVERRIDE_FSTYPE_ROOT=ext4
        # The kernel versions in CentOS Stream 9 doesn't support orphan_file, but later versions of
        # mkfs.ext4 enabled it by default, so we disable it explicitly.
        SYSTEMD_REPART_MKFS_OPTIONS_EXT4="-O ^orphan_file"

Packages=
        kernel-modules # For squashfs
mkosi: Package a erofs usr partition with signed verity Let's start moving towards a more involved partitioning setup to test our stuff more when using mkosi. The root partition is generated on boot with systemd-repart. CentOS supports neither erofs nor btrfs so we use squashfs and xfs instead. We also enable SecureBoot= locally for additional coverage. This and the use of verity means users need to run `mkosi genkey` once to generate the keys necessary to do secure boot and verity. 2023-05-08 17:06:41 +03:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`

			`[Match]`
			`Distribution=centos`
mkosi: Merge base and system images The only reason to have these split up is to be able to build extension images that use the base image as a base tree and install extra packages. Until we have such a use case, let's merge the base and system images to simplify things a bit. We keep the mkosi.images/ directory to not cause too many conflicts with the integration tests PR. 2024-03-27 13:07:52 +03:00
mkosi: Adapt configuration to take into account configuration rework In https://github.com/systemd/mkosi/pull/2847, the '@' specifier is removed, CLI arguments take priority over configuration files again and the "main" image is defined at the top level instead of in mkosi.images/. Additionally, not every setting from the top level configuration is inherited by the images in mkosi.images/ anymore, only settings which make sense to be inherited are inherited. This commit gets rid of all the usages of '@', moves the "main" image configuration from mkosi.images/system to the top level and gets rid of various hacks we had in place to deal with quirks of the old configuration parsing logic. We also remove usages of Images= and --append as these options are removed by the mentioned PR. 2024-07-08 13:59:52 +03:00			`[Distribution]`
mkosi: Build CentOS Stream 10 images by default CentOS Stream 10 has a newer util-linux which means the terminal gets correctly resized to the size specified by mkosi. This is a much nicer experience than CentOS Stream 9 where you're stuck on 80x24 so let's make CentOS Stream 10 the default release to build. 2024-07-18 09:46:14 +03:00			`Release=10`
mkosi: Adapt configuration to take into account configuration rework In https://github.com/systemd/mkosi/pull/2847, the '@' specifier is removed, CLI arguments take priority over configuration files again and the "main" image is defined at the top level instead of in mkosi.images/. Additionally, not every setting from the top level configuration is inherited by the images in mkosi.images/ anymore, only settings which make sense to be inherited are inherited. This commit gets rid of all the usages of '@', moves the "main" image configuration from mkosi.images/system to the top level and gets rid of various hacks we had in place to deal with quirks of the old configuration parsing logic. We also remove usages of Images= and --append as these options are removed by the mentioned PR. 2024-07-08 13:59:52 +03:00
mkosi: Merge base and system images The only reason to have these split up is to be able to build extension images that use the base image as a base tree and install extra packages. Until we have such a use case, let's merge the base and system images to simplify things a bit. We keep the mkosi.images/ directory to not cause too many conflicts with the integration tests PR. 2024-03-27 13:07:52 +03:00			`[Content]`
mkosi: Replace submodules with our own thing Unfortunately, git submodules break in all sorts of ways: - Various github workflows (dependabot, github pages) try to do a shallow clone of git submodules which does not work at all when the git repository is hosted on pagure (https://pagure.io/pagure/issue/5453, https://github.com/dependabot/dependabot-core/issues/9391). - If the git forge hosting the git repository uses SHA256, then it breaks our usage of it as a submodule as SHA256 repositories cannot be used as submodules in SHA1 repositories (src.opensuse.org moved to SHA256 which broke our usage of opensuse's systemd spec as a submodule). - git submodules completely break usage of git worktrees. - ... Let's avoid all these issues by just doing our own home grown implementation of git submodules. We lose the automatic dependabot updates this way but since dependabot fails to run more often that not with submodules we don't really lose anything. 2024-05-30 17:24:42 +03:00			`Environment=`
mkosi: Switch back to btrfs The next commit will introduce a way to iterate on integration tests which depends on btrfs specific features. We leave CentOS on ext4 as its kernel does not support btrfs. 2024-08-02 17:23:40 +03:00			`# CentOS doesn't support btrfs so we have to use something else. We'd prefer to use XFS here but it`
			`# fails to mount on duplicate filesystem UUIDs which happens when running tests in parallel so we use`
			`# ext4 instead.`
mkosi: Fix typo Our config parsing is flexible enough that this kind of worked surprisingly enough. 2024-07-18 13:53:53 +03:00			`SYSTEMD_REPART_OVERRIDE_FSTYPE_ROOT=ext4`
			`# The kernel versions in CentOS Stream 9 doesn't support orphan_file, but later versions of`
			`# mkfs.ext4 enabled it by default, so we disable it explicitly.`
			`SYSTEMD_REPART_MKFS_OPTIONS_EXT4="-O ^orphan_file"`
mkosi: Use the "default" root filesystem for each distribution Let's not insist on btrfs everywhere. 93440db8b5eae1244aaf5fecfa68050a8b26f3e3 switched us back to btrfs as we wanted to rely on the fact it records timestamps properly. Since we now prefer to do incremental builds on the host with "mkosi -t none" we don't mind anymore that timestamps are not recorded properly so we're not forced to use btrfs anymore. This also increases test coverage as we'll now test with different root filesystems. 2024-07-05 10:35:43 +03:00
mkosi: Merge base and system images The only reason to have these split up is to be able to build extension images that use the base image as a base tree and install extra packages. Until we have such a use case, let's merge the base and system images to simplify things a bit. We keep the mkosi.images/ directory to not cause too many conflicts with the integration tests PR. 2024-03-27 13:07:52 +03:00			`Packages=`
mkosi: Switch back to cloud/KVM kernel packages Now that we don't need megasas2 anymore, let's switch back to the KVM/cloud kernel images to save on image size, build times and boot times. 2024-05-28 15:09:57 +03:00			`kernel-modules # For squashfs`