man/systemd-dissect.xml

   1 <?xml version='1.0'?> <!--*-nxml-*-->
   2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   3   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
   4 <!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
   5
   6 <refentry id="systemd-dissect" conditional='HAVE_BLKID'
   7     xmlns:xi="http://www.w3.org/2001/XInclude">
   8
   9   <refentryinfo>
  10     <title>systemd-dissect</title>
  11     <productname>systemd</productname>
  12   </refentryinfo>
  13
  14   <refmeta>
  15     <refentrytitle>systemd-dissect</refentrytitle>
  16     <manvolnum>1</manvolnum>
  17   </refmeta>
  18
  19   <refnamediv>
  20     <refname>systemd-dissect</refname>
  21     <refname>mount.ddi</refname>
  22     <refpurpose>Dissect Discoverable Disk Images (DDIs)</refpurpose>
  23   </refnamediv>
  24
  25   <refsynopsisdiv>
  26     <cmdsynopsis>
  27       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <arg choice="plain"><replaceable>IMAGE</replaceable></arg></command>
  28     </cmdsynopsis>
  29     <cmdsynopsis>
  30       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--mount</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg> <arg choice="plain"><replaceable>PATH</replaceable></arg></command>
  31     </cmdsynopsis>
  32     <cmdsynopsis>
  33       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--umount</option> <arg choice="plain"><replaceable>PATH</replaceable></arg></command>
  34     </cmdsynopsis>
  35     <cmdsynopsis>
  36       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--attach</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg></command>
  37     </cmdsynopsis>
  38     <cmdsynopsis>
  39       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--detach</option> <arg choice="plain"><replaceable>PATH</replaceable></arg></command>
  40     </cmdsynopsis>
  41     <cmdsynopsis>
  42       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--list</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg></command>
  43     </cmdsynopsis>
  44     <cmdsynopsis>
  45       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--mtree</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg></command>
  46     </cmdsynopsis>
  47     <cmdsynopsis>
  48       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--with</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg> <arg choice="opt" rep="repeat"><replaceable>COMMAND</replaceable></arg></command>
  49     </cmdsynopsis>
  50     <cmdsynopsis>
  51       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--copy-from</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg> <arg choice="plain"><replaceable>PATH</replaceable></arg> <arg choice="opt"><replaceable>TARGET</replaceable></arg></command>
  52     </cmdsynopsis>
  53     <cmdsynopsis>
  54       <command>systemd-dissect <arg choice="opt" rep="repeat">OPTIONS</arg> <option>--copy-to</option> <arg choice="plain"><replaceable>IMAGE</replaceable></arg> <arg choice="opt"><replaceable>SOURCE</replaceable></arg> <arg choice="plain"><replaceable>PATH</replaceable></arg></command>
  55     </cmdsynopsis>
  56   </refsynopsisdiv>
  57
  58   <refsect1>
  59     <title>Description</title>
  60
  61     <para><command>systemd-dissect</command> is a tool for introspecting and interacting with file system OS
  62     disk images, specifically Discoverable Disk Images (DDIs). It supports four different operations:</para>
  63
  64     <orderedlist>
  65       <listitem><para>Show general OS image information, including the image's
  66       <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry> data,
  67       machine ID, partition information and more.</para></listitem>
  68
  69       <listitem><para>Mount an OS image to a local directory. In this mode it will dissect the OS image and
  70       mount the included partitions according to their designation onto a directory and possibly
  71       sub-directories.</para></listitem>
  72
  73       <listitem><para>Unmount an OS image from a local directory. In this mode it will recursively unmount
  74       the mounted partitions and remove the underlying loop device, including all the partition sub-devices.
  75       </para></listitem>
  76
  77       <listitem><para>Copy files and directories in and out of an OS image.</para></listitem>
  78     </orderedlist>
  79
  80     <para>The tool may operate on three types of OS images:</para>
  81
  82     <orderedlist>
  83       <listitem><para>OS disk images containing a GPT partition table envelope, with partitions marked
  84       according to the <ulink url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions
  85       Specification</ulink>.</para></listitem>
  86
  87       <listitem><para>OS disk images containing just a plain file-system without an enveloping partition
  88       table. (This file system is assumed to be the root file system of the OS.)</para></listitem>
  89
  90       <listitem><para>OS disk images containing a GPT or MBR partition table, with a single
  91       partition only. (This partition is assumed to contain the root file system of the OS.)</para></listitem>
  92     </orderedlist>
  93
  94     <para>OS images may use any kind of Linux-supported file systems. In addition they may make use of LUKS
  95     disk encryption, and contain Verity integrity information. Note that qualifying OS images may be booted
  96     with <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
  97     <option>--image=</option> switch, and be used as root file system for system service using the
  98     <varname>RootImage=</varname> unit file setting, see
  99     <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
 100
 101     <para>Note that the partition table shown when invoked without command switch (as listed below) does not
 102     necessarily show all partitions included in the image, but just the partitions that are understood and
 103     considered part of an OS disk image. Specifically, partitions of unknown types are ignored, as well as
 104     duplicate partitions (i.e. more than one per partition type), as are root and <filename>/usr/</filename>
 105     partitions of architectures not compatible with the local system. In other words: this tool will display
 106     what it operates with when mounting the image. To display the complete list of partitions use a tool such
 107     as <citerefentry
 108     project='man-pages'><refentrytitle>fdisk</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
 109
 110     <para>The <command>systemd-dissect</command> command may be invoked as <command>mount.ddi</command> in
 111     which case it implements the <citerefentry
 112     project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> "external
 113     helper" interface. This ensures disk images compatible with <command>systemd-dissect</command> can be
 114     mounted directly by <command>mount</command> and <citerefentry
 115     project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
 116     details see below.</para>
 117   </refsect1>
 118
 119   <refsect1>
 120     <title>Commands</title>
 121
 122     <para>If neither of the command switches listed below are passed the specified disk image is opened and
 123     general information about the image and the contained partitions and their use is shown.</para>
 124
 125     <variablelist>
 126       <varlistentry>
 127         <term><option>--mount</option></term>
 128         <term><option>-m</option></term>
 129
 130         <listitem><para>Mount the specified OS image to the specified directory. This will dissect the image,
 131         determine the OS root file system — as well as possibly other partitions — and mount them to the
 132         specified directory. If the OS image contains multiple partitions marked with the <ulink
 133         url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions Specification</ulink>
 134         multiple nested mounts are established. This command expects two arguments: a path to an image file
 135         and a path to a directory where to mount the image.</para>
 136
 137         <para>To unmount an OS image mounted like this use the <option>--umount</option> operation.</para>
 138
 139         <para>When the OS image contains LUKS encrypted or Verity integrity protected file systems
 140         appropriate volumes are automatically set up and marked for automatic disassembly when the image is
 141         unmounted.</para>
 142
 143         <para>The OS image may either be specified as path to an OS image stored in a regular file or may
 144         refer to block device node (in the latter case the block device must be the "whole" device, i.e. not
 145         a partition device). (The other supported commands described here support this, too.)</para>
 146
 147         <para>All mounted file systems are checked with the appropriate <citerefentry
 148         project='man-pages'><refentrytitle>fsck</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 149         implementation in automatic fixing mode, unless explicitly turned off (<option>--fsck=no</option>) or
 150         read-only operation is requested (<option>--read-only</option>).</para>
 151
 152         <para>Note that this functionality is also available in <citerefentry
 153         project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry> via a
 154         command such as <command>mount -t ddi myimage.raw targetdir/</command>, as well as in <citerefentry
 155         project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
 156         details, see below.</para></listitem>
 157       </varlistentry>
 158
 159       <varlistentry>
 160         <term><option>-M</option></term>
 161
 162         <listitem><para>This is a shortcut for <option>--mount --mkdir</option>.</para></listitem>
 163       </varlistentry>
 164
 165       <varlistentry>
 166         <term><option>--umount</option></term>
 167         <term><option>-u</option></term>
 168
 169         <listitem><para>Unmount an OS image from the specified directory. This command expects one argument:
 170         a directory where an OS image was mounted.</para>
 171
 172         <para>All mounted partitions will be recursively unmounted, and the underlying loop device will be
 173         removed, along with all its partition sub-devices.</para></listitem>
 174       </varlistentry>
 175
 176       <varlistentry>
 177         <term><option>-U</option></term>
 178
 179         <listitem><para>This is a shortcut for <option>--umount --rmdir</option>.</para></listitem>
 180       </varlistentry>
 181
 182       <varlistentry>
 183         <term><option>--attach</option></term>
 184
 185         <listitem><para>Attach the specified disk image to an automatically allocated loopback block device,
 186         and print the path to the loopback block device to standard output. This is similar to an invocation
 187         of <command>losetup --find --show</command>, but will validate the image as DDI before attaching, and
 188         derive the correct sector size to use automatically. Moreover, it ensures the per-partition block
 189         devices are created before returning. Takes a path to a disk image file.</para></listitem>
 190       </varlistentry>
 191
 192       <varlistentry>
 193         <term><option>--detach</option></term>
 194
 195         <listitem><para>Detach the specified disk image from a loopback block device. This undoes the effect
 196         of <option>--attach</option> above. This expects either a path to a loopback block device as an
 197         argument, or the path to the backing image file. In the latter case it will automatically determine
 198         the right device to detach.</para></listitem>
 199       </varlistentry>
 200
 201       <varlistentry>
 202         <term><option>--list</option></term>
 203         <term><option>-l</option></term>
 204
 205         <listitem><para>Prints the paths of all the files and directories in the specified OS image to
 206         standard output.</para></listitem>
 207       </varlistentry>
 208
 209       <varlistentry>
 210         <term><option>--mtree</option></term>
 211         <term><option>-l</option></term>
 212
 213         <listitem><para>Generates a BSD <citerefentry
 214         project='die-net'><refentrytitle>mtree</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 215         compatible file manifest of the specified disk image. This is useful for comparing disk image
 216         contents in detail, including inode information and other metadata. While the generated manifest will
 217         contain detailed inode information, it currently excludes extended attributes, file system
 218         capabilities, MAC labels, <citerefentry
 219         project='man-pages'><refentrytitle>chattr</refentrytitle><manvolnum>1</manvolnum></citerefentry> file
 220         flags, btrfs subvolume information, and various other file metadata. File content information is
 221         shown via a SHA256 digest. Additional fields might be added in future. Note that inode information
 222         such as link counts, inode numbers and timestamps is excluded from the output on purpose, as it
 223         typically complicates reproducibility.</para></listitem>
 224       </varlistentry>
 225
 226       <varlistentry>
 227         <term><option>--with</option></term>
 228
 229         <listitem><para>Runs the specified command with the specified OS image mounted. This will mount the
 230         image to a temporary directory, switch the current working directory to it, and invoke the specified
 231         command line as child process. Once the process ends it will unmount the image again, and remove the
 232         temporary directory. If no command is specified a shell is invoked. The image is mounted writable,
 233         use <option>--read-only</option> to switch to read-only operation. The invoked process will have the
 234         <varname>$SYSTEMD_DISSECT_ROOT</varname> environment variable set, containing the absolute path name
 235         of the temporary mount point, i.e. the same directory that is set as the current working
 236         directory.</para></listitem>
 237       </varlistentry>
 238
 239       <varlistentry>
 240         <term><option>--copy-from</option></term>
 241         <term><option>-x</option></term>
 242
 243         <listitem><para>Copies a file or directory from the specified OS image into the specified location on
 244         the host file system. Expects three arguments: a path to an image file, a source path (relative to
 245         the image's root directory) and a destination path (relative to the current working directory, or an
 246         absolute path, both outside of the image). If the destination path is omitted or specified as dash
 247         (<literal>-</literal>), the specified file is written to standard output. If the source path in the
 248         image file system refers to a regular file it is copied to the destination path. In this case access
 249         mode, extended attributes and timestamps are copied as well, but file ownership is not. If the source
 250         path in the image refers to a directory, it is copied to the destination path, recursively with all
 251         containing files and directories. In this case the file ownership is copied too.</para></listitem>
 252       </varlistentry>
 253
 254       <varlistentry>
 255         <term><option>--copy-to</option></term>
 256         <term><option>-a</option></term>
 257
 258         <listitem><para>Copies a file or directory from the specified location in the host file system into
 259         the specified OS image. Expects three arguments: a path to an image file, a source path (relative to
 260         the current working directory, or an absolute path, both outside of the image) and a destination path
 261         (relative to the image's root directory). If the source path is omitted or specified as dash
 262         (<literal>-</literal>), the data to write is read from standard input. If the source path in the host
 263         file system refers to a regular file, it is copied to the destination path. In this case access mode,
 264         extended attributes and timestamps are copied as well, but file ownership is not. If the source path
 265         in the host file system refers to a directory it is copied to the destination path, recursively with
 266         all containing files and directories. In this case the file ownership is copied
 267         too.</para>
 268
 269         <para>As with <option>--mount</option> file system checks are implicitly run before the copy
 270         operation begins.</para></listitem>
 271       </varlistentry>
 272
 273       <varlistentry>
 274         <term><option>--discover</option></term>
 275
 276         <listitem><para>Show a list of DDIs in well-known directories. This will show machine, portable
 277         service and system/configuration extension disk images in the usual directories
 278         <filename>/usr/lib/machines/</filename>, <filename>/usr/lib/portables/</filename>,
 279         <filename>/usr/lib/confexts/</filename>, <filename>/var/lib/machines/</filename>,
 280         <filename>/var/lib/portables/</filename>, <filename>/var/lib/extensions/</filename> and so
 281         on.</para></listitem>
 282       </varlistentry>
 283
 284       <varlistentry>
 285         <term><option>--validate</option></term>
 286
 287         <listitem><para>Validates the partition arrangement of a disk image (DDI), and ensures it matches the
 288         image policy specified via <option>--image-policy=</option>, if one is specified. This parses the
 289         partition table and probes the file systems in the image, but does not attempt to mount them (nor to
 290         set up disk encryption/authentication via LUKS/Verity). It does this taking the configured image
 291         dissection policy into account. Since this operation does not mount file systems, this command –
 292         unlike all other commands implemented by this tool – requires no privileges other than the ability to
 293         access the specified file. Prints "OK" and returns zero if the image appears to be in order and
 294         matches the specified image dissection policy. Otherwise prints an error message and returns
 295         non-zero.</para></listitem>
 296       </varlistentry>
 297
 298       <xi:include href="standard-options.xml" xpointer="help" />
 299       <xi:include href="standard-options.xml" xpointer="version" />
 300     </variablelist>
 301
 302   </refsect1>
 303
 304   <refsect1>
 305     <title>Options</title>
 306
 307     <para>The following options are understood:</para>
 308
 309     <variablelist>
 310       <varlistentry>
 311         <term><option>--read-only</option></term>
 312         <term><option>-r</option></term>
 313
 314         <listitem><para>Operate in read-only mode. By default <option>--mount</option> will establish
 315         writable mount points. If this option is specified they are established in read-only mode
 316         instead.</para></listitem>
 317       </varlistentry>
 318
 319       <varlistentry>
 320         <term><option>--fsck=no</option></term>
 321
 322         <listitem><para>Turn off automatic file system checking. By default when an image is accessed for
 323         writing (by <option>--mount</option> or <option>--copy-to</option>) the file systems contained in the
 324         OS image are automatically checked using the appropriate <citerefentry
 325         project='man-pages'><refentrytitle>fsck</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 326         command, in automatic fixing mode. This behavior may be switched off using
 327         <option>--fsck=no</option>.</para></listitem>
 328       </varlistentry>
 329
 330       <varlistentry>
 331         <term><option>--growfs=no</option></term>
 332
 333         <listitem><para>Turn off automatic growing of accessed file systems to their partition size, if
 334         marked for that in the GPT partition table. By default when an image is accessed for writing (by
 335         <option>--mount</option> or <option>--copy-to</option>) the file systems contained in the OS image
 336         are automatically grown to their partition sizes, if bit 59 in the GPT partition flags is set for
 337         partition types that are defined by the <ulink
 338         url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions Specification</ulink>. This
 339         behavior may be switched off using <option>--growfs=no</option>. File systems are grown automatically
 340         on access if all of the following conditions are met:</para>
 341         <orderedlist>
 342           <listitem><para>The file system is mounted writable</para></listitem>
 343           <listitem><para>The file system currently is smaller than the partition it is contained in (and thus can be grown)</para></listitem>
 344           <listitem><para>The image contains a GPT partition table</para></listitem>
 345           <listitem><para>The file system is stored on a partition defined by the Discoverable Partitions Specification</para></listitem>
 346           <listitem><para>Bit 59 of the GPT partition flags for this partition is set, as per specification</para></listitem>
 347           <listitem><para>The <option>--growfs=no</option> option is not passed.</para></listitem>
 348         </orderedlist>
 349         </listitem>
 350       </varlistentry>
 351
 352       <varlistentry>
 353         <term><option>--mkdir</option></term>
 354
 355         <listitem><para>If combined with <option>--mount</option> the directory to mount the OS image to is
 356         created if it is missing. Note that the directory is not automatically removed when the disk image is
 357         unmounted again.</para></listitem>
 358       </varlistentry>
 359
 360       <varlistentry>
 361         <term><option>--rmdir</option></term>
 362
 363         <listitem><para>If combined with <option>--umount</option> the specified directory where the OS image
 364         is mounted is removed after unmounting the OS image.</para></listitem>
 365       </varlistentry>
 366
 367       <varlistentry>
 368         <term><option>--discard=</option></term>
 369
 370         <listitem><para>Takes one of <literal>disabled</literal>, <literal>loop</literal>,
 371         <literal>all</literal>, <literal>crypto</literal>. If <literal>disabled</literal> the image is
 372         accessed with empty block discarding turned off. If <literal>loop</literal> discarding is enabled if
 373         operating on a regular file. If <literal>crypt</literal> discarding is enabled even on encrypted file
 374         systems. If <literal>all</literal> discarding is unconditionally enabled.</para></listitem>
 375       </varlistentry>
 376
 377       <varlistentry>
 378         <term><option>--in-memory</option></term>
 379
 380         <listitem><para>If specified an in-memory copy of the specified disk image is used. This may be used
 381         to operate with write-access on a (possibly read-only) image, without actually modifying the original
 382         file. This may also be used in order to operate on a disk image without keeping the originating file
 383         system busy, in order to allow it to be unmounted.</para></listitem>
 384       </varlistentry>
 385
 386       <varlistentry>
 387         <term><option>--root-hash=</option></term>
 388         <term><option>--root-hash-sig=</option></term>
 389         <term><option>--verity-data=</option></term>
 390
 391         <listitem><para>Configure various aspects of Verity data integrity for the OS image. Option
 392         <option>--root-hash=</option> specifies a hex-encoded top-level Verity hash to use for setting up the
 393         Verity integrity protection. Option <option>--root-hash-sig=</option> specifies the path to a file
 394         containing a PKCS#7 signature for the hash. This signature is passed to the kernel during activation,
 395         which will match it against signature keys available in the kernel keyring.  Option
 396         <option>--verity-data=</option> specifies a path to a file with the Verity data to use for the OS
 397         image, in case it is stored in a detached file. It is recommended to embed the Verity data directly
 398         in the image, using the Verity mechanisms in the <ulink
 399         url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions Specification</ulink>.
 400         </para></listitem>
 401       </varlistentry>
 402
 403       <varlistentry>
 404         <term><option>--loop-ref=</option></term>
 405
 406         <listitem><para>Configures the "reference" string the kernel shall report as backing file for the
 407         loopback block device. While this is supposed to be a path or filename referencing the backing file,
 408         this is not enforced and the kernel accepts arbitrary free-form strings, chosen by the user. Accepts
 409         arbitrary strings up to a length of 63 characters. This sets the kernel's
 410         <literal>.lo_file_name</literal> field for the block device. Note this is distinct from the
 411         <filename>/sys/class/block/loopX/loop/backing_file</filename> attribute file that always reports a
 412         path referring to the actual backing file. The latter is subject to mount namespace translation, the
 413         former is not.</para>
 414
 415         <para>This setting is particularly useful in combination with the <option>--attach</option> command,
 416         as it allows later referencing the allocated loop device via <filename>/dev/loop/by-ref/…</filename>
 417         symlinks. Example: first, set up the loopback device via <command>systemd-dissect attach
 418         --loop-ref=quux foo.raw</command>, and then reference it in a command via the specified filename:
 419         <command>cfdisk /dev/loop/by-ref/quux</command>.</para></listitem>
 420       </varlistentry>
 421
 422       <xi:include href="standard-options.xml" xpointer="image-policy-open" />
 423       <xi:include href="standard-options.xml" xpointer="no-pager" />
 424       <xi:include href="standard-options.xml" xpointer="no-legend" />
 425       <xi:include href="standard-options.xml" xpointer="json" />
 426     </variablelist>
 427   </refsect1>
 428
 429   <refsect1>
 430     <title>Exit status</title>
 431
 432     <para>On success, 0 is returned, a non-zero failure code otherwise. If the <option>--with</option>
 433     command is used the exit status of the invoked command is propagated.</para>
 434   </refsect1>
 435
 436   <refsect1>
 437     <title>Invocation as <command>/sbin/mount.ddi</command></title>
 438
 439     <para>The <command>systemd-dissect</command> executable may be symlinked to
 440     <filename>/sbin/mount.ddi</filename>. If invoked through that it implements <citerefentry
 441     project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>'s
 442     "external helper" interface for the (pseudo) file system type <literal>ddi</literal>. This means
 443     conformant disk images may be mounted directly via</para>
 444
 445     <programlisting># mount -t ddi myimage.raw targetdir/</programlisting>
 446
 447     <para>in a fashion mostly equivalent to:</para>
 448
 449     <programlisting># systemd-dissect --mount myimage.raw targetdir/</programlisting>
 450
 451     <para>Note that since a single DDI may contain multiple file systems it should later be unmounted with
 452     <command>umount -R targetdir/</command>, for recursive operation.</para>
 453
 454     <para>This functionality is particularly useful to mount DDIs automatically at boot via simple
 455     <filename>/etc/fstab</filename> entries. For example:</para>
 456
 457     <programlisting>/path/to/myimage.raw /images/myimage/ ddi defaults 0 0</programlisting>
 458
 459     <para>When invoked this way the mount options <literal>ro</literal>, <literal>rw</literal>,
 460     <literal>discard</literal>, <literal>nodiscard</literal> map to the corresponding options listed above
 461     (i.e. <option>--read-only</option>, <option>--discard=all</option>,
 462     <option>--discard=disabled</option>). Mount options are <emphasis>not</emphasis> generically passed on to
 463     the file systems inside the images.</para>
 464   </refsect1>
 465
 466   <refsect1>
 467     <title>Examples</title>
 468
 469     <example>
 470       <title>Generate a tarball from an OS disk image</title>
 471
 472       <programlisting># systemd-dissect --with foo.raw tar cz . >foo.tar.gz</programlisting>
 473     </example>
 474   </refsect1>
 475
 476   <refsect1>
 477     <title>See Also</title>
 478     <para>
 479       <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 480       <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 481       <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
 482       <ulink url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions Specification</ulink>,
 483       <citerefentry project='man-pages'><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 484       <citerefentry project='man-pages'><refentrytitle>umount</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
 485       <citerefentry project='man-pages'><refentrytitle>fdisk</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 486     </para>
 487   </refsect1>
 488
 489 </refentry>