From 16c1ca0db4cf6dd33cff1239df8dd9c366cee914 Mon Sep 17 00:00:00 2001 From: Kai Lueke Date: Tue, 9 Aug 2022 17:07:20 +0200 Subject: sysext: introduce ARCHITECTURE field to match host architecture When an extension image has binaries they should match the host architecture. Currently there is no way to specify this requirement. Introduce an ARCHITECTURE field in the extension's release file that may be set to prevent loading on the wrong host architecture. Since this new field is introduced late, we don't want to make specifying it mandatory as it would break existing sysext images. See https://github.com/systemd/systemd/issues/24061 --- man/os-release.xml | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'man/os-release.xml') diff --git a/man/os-release.xml b/man/os-release.xml index fc880c4765..168c1675a9 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -411,6 +411,18 @@ determines the fallback hostname. + + ARCHITECTURE= + A string that specifies which CPU architecture the userspace binaries require. + The architecture identifiers are the same as for ConditionArchitecture= + described in systemd.unit5. + The field is optional and should only be used when just single architecture is supported. + It may provide redundant information when used in a GPT partition with a GUID type that already + encodes the architecture. If this is not the case, the architecture should be specified in + e.g., an extension image, to prevent an incompatible host from loading it. + + + SYSEXT_LEVEL= -- cgit v1.2.1