From: Luca Boccassi Date: Mon, 17 Jan 2022 15:11:29 +0000 (+0000) Subject: man: add more references for extensions to portablectl X-Git-Tag: v251-rc1~513 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e91aa2ea23e17c3f589376aab626adc2096e97c7;p=thirdparty%2Fsystemd.git man: add more references for extensions to portablectl Link in systemd.io and systemd-sysext Fixes #22146 --- diff --git a/man/portablectl.xml b/man/portablectl.xml index c5404db0bae..f58275b1585 100644 --- a/man/portablectl.xml +++ b/man/portablectl.xml @@ -47,7 +47,8 @@ Portable service images are an efficient way to bundle multiple related services and other units together, and transfer them as a whole between systems. When these images are attached the local system the contained units may run in most ways like regular system-provided units, either with full privileges or inside strict sandboxing, - depending on the selected configuration. + depending on the selected configuration. For more details, see + Portable Services. Specifically portable service images may be of the following kind: @@ -359,10 +360,13 @@ top of IMAGE when attaching/detaching. This argument can be specified multiple times, in which case the order in which images are laid down follows the rules specified in systemd.exec5 - for the ExtensionImages= directive. The image(s) must contain an - extension-release file with metadata that matches what is defined in the - os-release of IMAGE. See: + for the ExtensionImages= directive and for the + systemd-sysext8 tool. + The image(s) must contain an extension-release file with metadata that matches + what is defined in the os-release of IMAGE. See: os-release5. + For more information on portable services with extensions, see the Extension Images + paragraph on Portable Services. Note that the same extensions have to be specified, in the same order, when attaching @@ -451,6 +455,7 @@ See Also systemd1, + systemd-sysext8, org.freedesktop.portable15, systemd-portabled.service8