Debian Codegraph @

upstream/debian-trixie/man8/systemd-sysext.8

raw
1 '\" t
2 .TH "SYSTEMD\-SYSEXT" "8" "" "systemd 257.13" "systemd-sysext"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd-sysext, systemd-sysext.service, systemd-confext, systemd-confext.service \- Activates System Extension Images
24 .SH "SYNOPSIS"
25 .HP \w'\fBsystemd\-sysext\fR\ 'u
26 \fBsystemd\-sysext\fR [OPTIONS...] COMMAND
27 .PP
28 systemd\-sysext\&.service
29 .HP \w'\fBsystemd\-confext\fR\ 'u
30 \fBsystemd\-confext\fR [OPTIONS...] COMMAND
31 .PP
32 systemd\-confext\&.service
33 .SH "DESCRIPTION"
34 .PP
35 \fBsystemd\-sysext\fR
36 activates/deactivates system extension images\&. System extension images may \(en dynamically at runtime \(em extend the
37 /usr/
38 and
39 /opt/
40 directory hierarchies with additional files\&. This is particularly useful on immutable system images where a
41 /usr/
42 and/or
43 /opt/
44 hierarchy residing on a read\-only file system shall be extended temporarily at runtime without making any persistent modifications\&.
45 .PP
46 System extension images should contain files and directories similar in fashion to regular operating system tree\&. When one or more system extension images are activated, their
47 /usr/
48 and
49 /opt/
50 hierarchies are combined via
51 "overlayfs"
52 with the same hierarchies of the host OS, and the host
53 /usr/
54 and
55 /opt/
56 overmounted with it ("merging")\&. When they are deactivated, the mount point is disassembled \(em again revealing the unmodified original host version of the hierarchy ("unmerging")\&. Merging thus makes the extension\*(Aqs resources suddenly appear below the
57 /usr/
58 and
59 /opt/
60 hierarchies as if they were included in the base OS image itself\&. Unmerging makes them disappear again, leaving in place only the files that were shipped with the base OS image itself\&.
61 .PP
62 Files and directories contained in the extension images outside of the
63 /usr/
64 and
65 /opt/
66 hierarchies are
67 \fInot\fR
68 merged, and hence have no effect when included in a system extension image\&. In particular, files in the
69 /etc/
70 and
71 /var/
72 included in a system extension image will
73 \fInot\fR
74 appear in the respective hierarchies after activation\&.
75 .PP
76 System extension images are strictly read\-only by default\&. On mutable host file systems,
77 /usr/
78 and
79 /opt/
80 hierarchies become read\-only while extensions are merged, unless mutability is enabled\&. Mutability may be enabled via the
81 \fB\-\-mutable=\fR
82 option; see "Mutability" below for more information\&.
83 .PP
84 System extensions are supposed to be purely additive, i\&.e\&. they are supposed to include only files that do not exist in the underlying basic OS image\&. However, the underlying mechanism (overlayfs) also allows overlaying or removing files, but it is recommended not to make use of this\&.
85 .PP
86 System extension images may be provided in the following formats:
87 .sp
88 .RS 4
89 .ie n \{\
90 \h'-04' 1.\h'+01'\c
91 .\}
92 .el \{\
93 .sp -1
94 .IP " 1." 4.2
95 .\}
96 Plain directories or btrfs subvolumes containing the OS tree
97 .RE
98 .sp
99 .RS 4
100 .ie n \{\
101 \h'-04' 2.\h'+01'\c
102 .\}
103 .el \{\
104 .sp -1
105 .IP " 2." 4.2
106 .\}
107 Disk images with a GPT disk label, following the
108 \m[blue]\fBDiscoverable Partitions Specification\fR\m[]\&\s-2\u[1]\d\s+2
109 .RE
110 .sp
111 .RS 4
112 .ie n \{\
113 \h'-04' 3.\h'+01'\c
114 .\}
115 .el \{\
116 .sp -1
117 .IP " 3." 4.2
118 .\}
119 Disk images lacking a partition table, with a naked Linux file system (e\&.g\&. erofs, squashfs or ext4)
120 .RE
121 .PP
122 These image formats are the same ones that
123 \fBsystemd-nspawn\fR(1)
124 supports via its
125 \fB\-\-directory=\fR/\fB\-\-image=\fR
126 switches and those that the service manager supports via
127 \fBRootDirectory=\fR/\fBRootImage=\fR\&. Similar to them they may optionally carry Verity authentication information\&.
128 .PP
129 System extensions are searched for in the directories
130 /etc/extensions/,
131 /run/extensions/
132 and
133 /var/lib/extensions/\&. The first two listed directories are not suitable for carrying large binary images, however are still useful for carrying symlinks to them\&. The primary place for installing system extensions is
134 /var/lib/extensions/\&. Any directories found in these search directories are considered directory based extension images; any files with the
135 \&.raw
136 suffix are considered disk image based extension images\&. When invoked in the initrd, the additional directory
137 /\&.extra/sysext/
138 is included in the directories that are searched for extension images\&. Note however, that by default a tighter image policy applies to images found there, though, see below\&. This directory is populated by
139 \fBsystemd-stub\fR(7)
140 with extension images found in the system\*(Aqs EFI System Partition\&.
141 .PP
142 During boot OS extension images are activated automatically, if the
143 systemd\-sysext\&.service
144 is enabled\&. Note that this service runs only after the underlying file systems where system extensions may be located have been mounted\&. This means they are not suitable for shipping resources that are processed by subsystems running in earliest boot\&. Specifically, OS extension images are not suitable for shipping system services or
145 \fBsystemd-sysusers\fR(8)
146 definitions\&. See the
147 \m[blue]\fBPortable Services\fR\m[]\&\s-2\u[2]\d\s+2
148 page for a simple mechanism for shipping system services in disk images, in a similar fashion to OS extensions\&. Note the different isolation on these two mechanisms: while system extension directly extend the underlying OS image with additional files that appear in a way very similar to as if they were shipped in the OS image itself and thus imply no security isolation, portable services imply service level sandboxing in one way or another\&. The
149 systemd\-sysext\&.service
150 service is guaranteed to finish start\-up before
151 basic\&.target
152 is reached; i\&.e\&. at the time regular services initialize (those which do not use
153 \fIDefaultDependencies=no\fR), the files and directories system extensions provide are available in
154 /usr/
155 and
156 /opt/
157 and may be accessed\&.
158 .PP
159 Note that there is no concept of enabling/disabling installed system extension images: all installed extension images are automatically activated at boot\&. However, you can place an empty directory named like the extension (no
160 \&.raw) in
161 /etc/extensions/
162 to "mask" an extension with the same name in a system folder with lower precedence\&.
163 .PP
164 A simple mechanism for version compatibility is enforced: a system extension image must carry a
165 /usr/lib/extension\-release\&.d/extension\-release\&.\fINAME\fR
166 file, which must match its image name, that is compared with the host
167 os\-release
168 file: the contained
169 \fIID=\fR
170 fields have to match unless
171 "_any"
172 is set for the extension\&. If the extension
173 \fIID=\fR
174 is not
175 "_any", the
176 \fISYSEXT_LEVEL=\fR
177 field (if defined) has to match\&. If the latter is not defined, the
178 \fIVERSION_ID=\fR
179 field has to match instead\&. If the extension defines the
180 \fIARCHITECTURE=\fR
181 field and the value is not
182 "_any"
183 it has to match the kernel\*(Aqs architecture reported by
184 \fBuname\fR(2)
185 but the used architecture identifiers are the same as for
186 \fIConditionArchitecture=\fR
187 described in
188 \fBsystemd.unit\fR(5)\&.
189 \fIEXTENSION_RELOAD_MANAGER=\fR
190 can be set to 1 if the extension requires a service manager reload after application of the extension\&. Note that for the reasons mentioned earlier,
191 \m[blue]\fBPortable Services\fR\m[]\&\s-2\u[2]\d\s+2
192 remain the recommended way to ship system services\&. System extensions should not ship a
193 /usr/lib/os\-release
194 file (as that would be merged into the host
195 /usr/
196 tree, overriding the host OS version data, which is not desirable)\&. The
197 extension\-release
198 file follows the same format and semantics, and carries the same content, as the
199 os\-release
200 file of the OS, but it describes the resources carried in the extension image\&.
201 .PP
202 The
203 \fBsystemd\-confext\fR
204 concept follows the same principle as the
205 \fBsystemd-sysext\fR(8)
206 functionality but instead of working on
207 /usr
208 and
209 /opt,
210 \fBconfext\fR
211 will extend only
212 /etc\&. Files and directories contained in the confext images outside of the
213 /etc/
214 hierarchy are
215 \fInot\fR
216 merged, and hence have no effect when included in the image\&. Formats for these images are of the same as sysext images\&. The merged hierarchy will be mounted with
217 "nosuid"
218 and (if not disabled via
219 \fB\-\-noexec=false\fR)
220 "noexec"\&.
221 .PP
222 Just like sysexts, confexts are strictly read\-only by default\&. Merging confexts on mutable host file systems will result in
223 /etc/
224 becoming read\-only\&. As with sysexts, mutability can be enabled via the
225 \fB\-\-mutable=\fR
226 option\&. Refer to "Mutability" below for more information\&.
227 .PP
228 Confexts are looked for in the directories
229 /run/confexts/,
230 /var/lib/confexts/,
231 /usr/lib/confexts/
232 and
233 /usr/local/lib/confexts/\&. The first listed directory is not suitable for carrying large binary images, however is still useful for carrying symlinks to them\&. The primary place for installing configuration extensions is
234 /var/lib/confexts/\&. Any directories found in these search directories are considered directory based confext images; any files with the
235 \&.raw
236 suffix are considered disk image based confext images\&.
237 .PP
238 Again, just like sysext images, the confext images will contain a
239 /etc/extension\-release\&.d/extension\-release\&.\fINAME\fR
240 file, which must match the image name (with the usual escape hatch of the
241 \fIuser\&.extension\-release\&.strict\fR
242 \fBxattr\fR(7)), and again with content being one or more of
243 \fIID=\fR,
244 \fIVERSION_ID=\fR, and
245 \fICONFEXT_LEVEL\fR\&. Confext images will then be checked and matched against the base OS layer\&.
246 .SH "USES"
247 .PP
248 The primary use case for system images are immutable environments where debugging and development tools shall optionally be made available, but not included in the immutable base OS image itself (e\&.g\&.
249 \fBstrace\fR(1)
250 and
251 \fBgdb\fR(1)
252 shall be an optionally installable addition in order to make debugging/development easier)\&. System extension images should not be misunderstood as a generic software packaging framework, as no dependency scheme is available: system extensions should carry all files they need themselves, except for those already shipped in the underlying host system image\&. Typically, system extension images are built at the same time as the base OS image \(em within the same build system\&.
253 .PP
254 Another use case for the system extension concept is temporarily overriding OS supplied resources with newer ones, for example to install a locally compiled development version of some low\-level component over the immutable OS image without doing a full OS rebuild or modifying the nominally immutable image\&. (e\&.g\&. "install" a locally built package with
255 \fBDESTDIR=/var/lib/extensions/mytest make install && systemd\-sysext refresh\fR, making it available in
256 /usr/
257 as if it was installed in the OS image itself\&.) This case works regardless if the underlying host
258 /usr/
259 is managed as immutable disk image or is a traditional package manager controlled (i\&.e\&. writable) tree\&.
260 .PP
261 With
262 \fBsystemd\-confext\fR
263 one can perform runtime reconfiguration of OS services\&. Sometimes, there is a need to swap certain configuration parameter values or restart only a specific service without deployment of new code or a complete OS deployment\&. In other words, we want to be able to tie the most frequently configured options to runtime updateable flags that can be changed without a system reboot\&. This will help reduce servicing times when there is a need for changing the OS configuration\&. It also provides a reliable tool for managing configuration because all old configuration files disappear when the
264 \fBsystemd\-confext\fR
265 image is removed\&.
266 .SH "MUTABILITY"
267 .PP
268 By default, merging system extensions on mutable host file systems will render
269 /usr/
270 and
271 /opt/
272 hierarchies read\-only\&. Merging configuration extensions will have the same effect on
273 /etc/\&. Mutable mode allows writes to these locations when extensions are merged\&.
274 .PP
275 The following modes are supported:
276 .sp
277 .RS 4
278 .ie n \{\
279 \h'-04' 1.\h'+01'\c
280 .\}
281 .el \{\
282 .sp -1
283 .IP " 1." 4.2
284 .\}
285 \fBdisabled\fR: Force immutable mode even if write routing directories exist below
286 /var/lib/extensions\&.mutable/\&. This is the default\&.
287 .RE
288 .sp
289 .RS 4
290 .ie n \{\
291 \h'-04' 2.\h'+01'\c
292 .\}
293 .el \{\
294 .sp -1
295 .IP " 2." 4.2
296 .\}
297 \fBauto\fR: Automatic mode\&. Mutability is disabled by default and only enabled if a corresponding write routing directory exists below
298 /var/lib/extensions\&.mutable/\&.
299 .RE
300 .sp
301 .RS 4
302 .ie n \{\
303 \h'-04' 3.\h'+01'\c
304 .\}
305 .el \{\
306 .sp -1
307 .IP " 3." 4.2
308 .\}
309 \fBenabled\fR: Force mutable mode and automatically create write routing directories below
310 /var/lib/extensions\&.mutable/
311 when required\&.
312 .RE
313 .sp
314 .RS 4
315 .ie n \{\
316 \h'-04' 4.\h'+01'\c
317 .\}
318 .el \{\
319 .sp -1
320 .IP " 4." 4.2
321 .\}
322 \fBimport\fR: Force immutable mode like
323 \fBdisabled\fR
324 above, but merge the contents of directories below
325 /var/lib/extensions\&.mutable/
326 into the host file system\&.
327 .RE
328 .sp
329 .RS 4
330 .ie n \{\
331 \h'-04' 5.\h'+01'\c
332 .\}
333 .el \{\
334 .sp -1
335 .IP " 5." 4.2
336 .\}
337 \fBephemeral\fR: Force mutable mode like
338 \fBenabled\fR
339 above, but instead of using write routing directory below
340 /var/lib/extensions\&.mutable/,
341 \fBsystemd\-sysext\fR
342 will use empty ephemeral directories\&. This means that the modifications made in the merged hierarchies will be gone when the hierarchies are unmerged\&.
343 .RE
344 .sp
345 .RS 4
346 .ie n \{\
347 \h'-04' 6.\h'+01'\c
348 .\}
349 .el \{\
350 .sp -1
351 .IP " 6." 4.2
352 .\}
353 \fBephemeral\-import\fR: Force mutable mode like
354 \fBephemeral\fR
355 above, but instead of ignoring the contents of write routing directories under
356 /var/lib/extensions\&.mutable/, merge them into the host file system, like
357 \fBimport\fR
358 does\&.
359 .RE
360 .sp
361 See "Options" below on specifying modes using the
362 \fB\-\-mutable=\fR
363 command line option\&.
364 .PP
365 With exception of the ephemeral mode, the mutable mode routes writes to subdirectories in
366 /var/lib/extensions\&.mutable/\&.
367 .RS 4
368 Writes to /usr/ are directed to /var/lib/extensions\&.mutable/usr/
369 .RE
370 .RS 4
371 writes to /opt/ are directed to /var/lib/extensions\&.mutable/opt/, and
372 .RE
373 .RS 4
374 writes to /etc/ land in /var/lib/extensions\&.mutable/etc/\&.
375 .RE
376 .PP
377 If
378 usr/,
379 opt/, or
380 etc/
381 in
382 /var/lib/extensions\&.mutable/
383 are symlinks, then writes are directed to the symlinks\*(Aq targets\&. Consequently, to retain mutability of a host file system, create symlinks
384 .RS 4
385 /var/lib/extensions\&.mutable/etc/ → /etc/
386 .RE
387 .RS 4
388 /var/lib/extensions\&.mutable/usr/ → /usr/
389 .RE
390 .RS 4
391 /var/lib/extensions\&.mutable/opt/ → /opt/
392 .RE
393 to route writes back to the original base directory hierarchy\&.
394 .PP
395 Alternatively, a temporary file system may be mounted to
396 /var/lib/extensions\&.mutable/, or symlinks in
397 /var/lib/extensions\&.mutable/
398 may point to sub\-directories on a temporary file system (e\&.g\&. below
399 /tmp/) to only allow ephemeral changes\&. Note that this is not the same as ephemeral mode, because the temporary file system will still exist after unmerging\&.
400 .PP
401 Added in version 256\&.
402 .SH "COMMANDS"
403 .PP
404 The following commands are understood by both the sysext and confext concepts:
405 .PP
406 \fBstatus\fR
407 .RS 4
408 When invoked without any command verb, or when
409 \fBstatus\fR
410 is specified the current merge status is shown, separately (for both
411 /usr/
412 and
413 /opt/
414 of sysext and for
415 /etc/
416 of confext)\&.
417 .sp
418 Added in version 248\&.
419 .RE
420 .PP
421 \fBmerge\fR
422 .RS 4
423 Merges all currently installed system extension images into
424 /usr/
425 and
426 /opt/, by overmounting these hierarchies with an
427 "overlayfs"
428 file system combining the underlying hierarchies with those included in the extension images\&. This command will fail if the hierarchies are already merged\&. For confext, the merge happens into the
429 /etc/
430 directory instead\&.
431 .sp
432 Added in version 248\&.
433 .RE
434 .PP
435 \fBunmerge\fR
436 .RS 4
437 Unmerges all currently installed system extension images from
438 /usr/
439 and
440 /opt/
441 for sysext and
442 /etc/, for confext, by unmounting the
443 "overlayfs"
444 file systems created by
445 \fBmerge\fR
446 prior\&.
447 .sp
448 Added in version 248\&.
449 .RE
450 .PP
451 \fBrefresh\fR
452 .RS 4
453 A combination of
454 \fBunmerge\fR
455 and
456 \fBmerge\fR: if already mounted the existing
457 "overlayfs"
458 instance is unmounted temporarily, and then replaced by a new version\&. This command is useful after installing/removing system extension images, in order to update the
459 "overlayfs"
460 file system accordingly\&. If no system extensions are installed when this command is executed, the equivalent of
461 \fBunmerge\fR
462 is executed, without establishing any new
463 "overlayfs"
464 instance\&. Note that currently there\*(Aqs a brief moment where neither the old nor the new
465 "overlayfs"
466 file system is mounted\&. This implies that all resources supplied by a system extension will briefly disappear \(em even if it exists continuously during the refresh operation\&.
467 .sp
468 Added in version 248\&.
469 .RE
470 .PP
471 \fBlist\fR
472 .RS 4
473 A brief list of installed extension images is shown\&.
474 .sp
475 Added in version 248\&.
476 .RE
477 .PP
478 \fB\-h\fR, \fB\-\-help\fR
479 .RS 4
480 Print a short help text and exit\&.
481 .RE
482 .PP
483 \fB\-\-version\fR
484 .RS 4
485 Print a short version string and exit\&.
486 .RE
487 .SH "OPTIONS"
488 .PP
489 \fB\-\-root=\fR
490 .RS 4
491 Operate relative to the specified root directory, i\&.e\&. establish the
492 "overlayfs"
493 mount not on the top\-level host
494 /usr/
495 and
496 /opt/
497 hierarchies for sysext or
498 /etc/
499 for confext, but below some specified root directory\&.
500 .sp
501 Added in version 248\&.
502 .RE
503 .PP
504 \fB\-\-force\fR
505 .RS 4
506 When merging system extensions into
507 /usr/
508 and
509 /opt/
510 for sysext and
511 /etc/
512 for confext, ignore version incompatibilities, i\&.e\&. force merging regardless of whether the version information included in the images matches the host or not\&.
513 .sp
514 Added in version 248\&.
515 .RE
516 .PP
517 \fB\-\-image\-policy=\fR\fB\fIpolicy\fR\fR
518 .RS 4
519 Takes an image policy string as argument, as per
520 \fBsystemd.image-policy\fR(7)\&. The policy is enforced when operating on system extension disk images\&. If not specified, defaults to
521 "root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent"
522 for system extensions, i\&.e\&. only the root and
523 /usr/
524 file systems in the image are used\&. For configuration extensions defaults to
525 "root=verity+signed+encrypted+unprotected+absent"\&. When run in the initrd and operating on a system extension image stored in the
526 /\&.extra/sysext/
527 directory a slightly stricter policy is used by default:
528 "root=signed+absent:usr=signed+absent", see above for details\&.
529 .sp
530 Added in version 254\&.
531 .RE
532 .PP
533 \fB\-\-mutable=\fR\fB\fIBOOL\fR\fR\fB|\fR\fB\fIauto\fR\fR\fB|\fR\fB\fIimport\fR\fR
534 .RS 4
535 Set mutable mode\&.
536 .PP
537 \fBno\fR
538 .RS 4
539 force immutable mode even with write routing directories present\&. This is the default\&.
540 .sp
541 Added in version 256\&.
542 .RE
543 .PP
544 \fBauto\fR
545 .RS 4
546 enable mutable mode individually for
547 /usr/,
548 /opt/, and
549 /etc/
550 if write routing sub\-directories or symlinks are present in
551 /var/lib/extensions\&.mutable/; disable otherwise\&. See "Mutability" above for more information on write routing\&.
552 .sp
553 Added in version 256\&.
554 .RE
555 .PP
556 \fByes\fR
557 .RS 4
558 force mutable mode\&. Write routing directories will be created in
559 /var/lib/extensions\&.mutable/
560 if not present\&.
561 .sp
562 Added in version 256\&.
563 .RE
564 .PP
565 \fBimport\fR
566 .RS 4
567 immutable mode, but with contents of write routing directories in
568 /var/lib/extensions\&.mutable/
569 also merged into the host file system\&.
570 .sp
571 Added in version 256\&.
572 .RE
573 .PP
574 \fBephemeral\fR
575 .RS 4
576 force mutable mode, but with contents of write routing directories in
577 /var/lib/extensions\&.mutable/
578 being ignored, and modifications of the host file system being discarded after unmerge\&.
579 .sp
580 Added in version 256\&.
581 .RE
582 .PP
583 \fBephemeral\-import\fR
584 .RS 4
585 force mutable mode, with contents of write routing directories in
586 /var/lib/extensions\&.mutable/
587 being merged into the host file system, but with the modifications made to the host file system being discarded after unmerge\&.
588 .sp
589 Added in version 256\&.
590 .RE
591 .sp
592 Added in version 256\&.
593 .RE
594 .PP
595 \fB\-\-noexec=\fR\fB\fIBOOL\fR\fR
596 .RS 4
597 When merging configuration extensions into
598 /etc/
599 the
600 "MS_NOEXEC"
601 mount flag is used by default\&. This option can be used to disable it\&.
602 .sp
603 Added in version 254\&.
604 .RE
605 .PP
606 \fB\-\-no\-reload\fR
607 .RS 4
608 When used with
609 \fBmerge\fR,
610 \fBunmerge\fR
611 or
612 \fBrefresh\fR, do not reload daemon after executing the changes even if an extension that is applied requires a reload via the
613 \fIEXTENSION_RELOAD_MANAGER=\fR
614 set to 1\&.
615 .sp
616 Added in version 255\&.
617 .RE
618 .PP
619 \fB\-\-no\-pager\fR
620 .RS 4
621 Do not pipe output into a pager\&.
622 .RE
623 .PP
624 \fB\-\-no\-legend\fR
625 .RS 4
626 Do not print the legend, i\&.e\&. column headers and the footer with hints\&.
627 .RE
628 .PP
629 \fB\-\-json=\fR\fB\fIMODE\fR\fR
630 .RS 4
631 Shows output formatted as JSON\&. Expects one of
632 "short"
633 (for the shortest possible output without any redundant whitespace or line breaks),
634 "pretty"
635 (for a pretty version of the same, with indentation and line breaks) or
636 "off"
637 (to turn off JSON output, the default)\&.
638 .RE
639 .SH "EXIT STATUS"
640 .PP
641 On success, 0 is returned\&.
642 .SH "SEE ALSO"
643 .PP
644 \fBsystemd\fR(1), \fBsystemd-nspawn\fR(1), \fBsystemd-stub\fR(7), \fBimportctl\fR(1)
645 .SH "NOTES"
646 .IP " 1." 4
647 Discoverable Partitions Specification
648 .RS 4
649 \%https://uapi-group.org/specifications/specs/discoverable_partitions_specification
650 .RE
651 .IP " 2." 4
652 Portable Services
653 .RS 4
654 \%https://systemd.io/PORTABLE_SERVICES
655 .RE