man/systemd.nspawn.xml

   1 <?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*-->
   2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
   3   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
   4 <!ENTITY % entities SYSTEM "custom-entities.ent" >
   5 %entities;
   6 ]>
   7
   8 <!--
   9   SPDX-License-Identifier: LGPL-2.1+
  10 -->
  11
  12 <refentry id="systemd.nspawn">
  13
  14   <refentryinfo>
  15     <title>systemd.nspawn</title>
  16     <productname>systemd</productname>
  17
  18     <authorgroup>
  19       <author>
  20         <contrib>Developer</contrib>
  21         <firstname>Lennart</firstname>
  22         <surname>Poettering</surname>
  23         <email>lennart@poettering.net</email>
  24       </author>
  25     </authorgroup>
  26   </refentryinfo>
  27
  28   <refmeta>
  29     <refentrytitle>systemd.nspawn</refentrytitle>
  30     <manvolnum>5</manvolnum>
  31   </refmeta>
  32
  33   <refnamediv>
  34     <refname>systemd.nspawn</refname>
  35     <refpurpose>Container settings</refpurpose>
  36   </refnamediv>
  37
  38   <refsynopsisdiv>
  39     <para><filename>/etc/systemd/nspawn/<replaceable>machine</replaceable>.nspawn</filename></para>
  40     <para><filename>/run/systemd/nspawn/<replaceable>machine</replaceable>.nspawn</filename></para>
  41     <para><filename>/var/lib/machines/<replaceable>machine</replaceable>.nspawn</filename></para>
  42   </refsynopsisdiv>
  43
  44   <refsect1>
  45     <title>Description</title>
  46
  47     <para>An nspawn container settings file (suffix
  48     <filename>.nspawn</filename>) encodes additional runtime
  49     information about a local container, and is searched, read and
  50     used by
  51     <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
  52     when starting a container. Files of this type are named after the
  53     containers they define settings for. They are optional, and only
  54     required for containers whose execution environment shall differ
  55     from the defaults. Files of this type mostly contain settings that
  56     may also be set on the <command>systemd-nspawn</command> command
  57     line, and make it easier to persistently attach specific settings
  58     to specific containers. The syntax of these files is inspired by
  59     <filename>.desktop</filename> files following the <ulink
  60     url="http://standards.freedesktop.org/desktop-entry-spec/latest/">XDG
  61     Desktop Entry Specification</ulink>, which in turn are inspired by
  62     Microsoft Windows <filename>.ini</filename> files.</para>
  63
  64     <para>Boolean arguments used in these settings files can be
  65     written in various formats. For positive settings, the strings
  66     <option>1</option>, <option>yes</option>, <option>true</option>
  67     and <option>on</option> are equivalent. For negative settings, the
  68     strings <option>0</option>, <option>no</option>,
  69     <option>false</option> and <option>off</option> are
  70     equivalent.</para>
  71
  72     <para>Empty lines and lines starting with # or ; are
  73     ignored. This may be used for commenting. Lines ending
  74     in a backslash are concatenated with the following
  75     line while reading and the backslash is replaced by a
  76     space character. This may be used to wrap long lines.</para>
  77
  78   </refsect1>
  79
  80   <refsect1>
  81     <title><filename>.nspawn</filename> File Discovery</title>
  82
  83     <para>Files are searched by appending the
  84     <filename>.nspawn</filename> suffix to the machine name of the
  85     container, as specified with the <option>--machine=</option>
  86     switch of <command>systemd-nspawn</command>, or derived from the
  87     directory or image file name. This file is first searched in
  88     <filename>/etc/systemd/nspawn/</filename> and
  89     <filename>/run/systemd/nspawn/</filename>. If found in these
  90     directories, its settings are read and all of them take full effect
  91     (but are possibly overridden by corresponding command line
  92     arguments). If not found, the file will then be searched next to
  93     the image file or in the immediate parent of the root directory of
  94     the container. If the file is found there, only a subset of the
  95     settings will take effect however. All settings that possibly
  96     elevate privileges or grant additional access to resources of the
  97     host (such as files or directories) are ignored. To which options
  98     this applies is documented below.</para>
  99
 100     <para>Persistent settings files created and maintained by the
 101     administrator (and thus trusted) should be placed in
 102     <filename>/etc/systemd/nspawn/</filename>, while automatically
 103     downloaded (and thus potentially untrusted) settings files are
 104     placed in <filename>/var/lib/machines/</filename> instead (next to
 105     the container images), where their security impact is limited. In
 106     order to add privileged settings to <filename>.nspawn</filename>
 107     files acquired from the image vendor, it is recommended to copy the
 108     settings files into <filename>/etc/systemd/nspawn/</filename> and
 109     edit them there, so that the privileged options become
 110     available. The precise algorithm for how the files are searched and
 111     interpreted may be configured with
 112     <command>systemd-nspawn</command>'s <option>--settings=</option>
 113     switch, see
 114     <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
 115     for details.</para>
 116   </refsect1>
 117
 118   <refsect1>
 119     <title>[Exec] Section Options</title>
 120
 121     <para>Settings files may include an <literal>[Exec]</literal>
 122     section, which carries various execution parameters:</para>
 123
 124     <variablelist>
 125
 126       <varlistentry>
 127         <term><varname>Boot=</varname></term>
 128
 129         <listitem><para>Takes a boolean argument, which defaults to off. If enabled, <command>systemd-nspawn</command>
 130         will automatically search for an <filename>init</filename> executable and invoke it. In this case, the
 131         specified parameters using <varname>Parameters=</varname> are passed as additional arguments to the
 132         <filename>init</filename> process. This setting corresponds to the <option>--boot</option> switch on the
 133         <command>systemd-nspawn</command> command line. This option may not be combined with
 134         <varname>ProcessTwo=yes</varname>. This option is the default if the
 135         <filename>systemd-nspawn@.service</filename> template unit file is used.</para></listitem>
 136       </varlistentry>
 137
 138       <varlistentry>
 139         <term><varname>ProcessTwo=</varname></term>
 140
 141         <listitem><para>Takes a boolean argument, which defaults to off. If enabled, the specified program is run as
 142         PID 2. A stub init process is run as PID 1. This setting corresponds to the <option>--as-pid2</option> switch
 143         on the <command>systemd-nspawn</command> command line. This option may not be combined with
 144         <varname>Boot=yes</varname>.</para></listitem>
 145       </varlistentry>
 146
 147       <varlistentry>
 148         <term><varname>Parameters=</varname></term>
 149
 150         <listitem><para>Takes a space-separated list of
 151         arguments. This is either a command line, beginning with the
 152         binary name to execute, or – if <varname>Boot=</varname> is
 153         enabled – the list of arguments to pass to the init
 154         process. This setting corresponds to the command line
 155         parameters passed on the <command>systemd-nspawn</command>
 156         command line.</para></listitem>
 157       </varlistentry>
 158
 159       <varlistentry>
 160         <term><varname>Environment=</varname></term>
 161
 162         <listitem><para>Takes an environment variable assignment
 163         consisting of key and value, separated by
 164         <literal>=</literal>. Sets an environment variable for the
 165         main process invoked in the container. This setting may be
 166         used multiple times to set multiple environment variables. It
 167         corresponds to the <option>--setenv=</option> command line
 168         switch.</para></listitem>
 169       </varlistentry>
 170
 171       <varlistentry>
 172         <term><varname>User=</varname></term>
 173
 174         <listitem><para>Takes a UNIX user name. Specifies the user
 175         name to invoke the main process of the container as. This user
 176         must be known in the container's user database. This
 177         corresponds to the <option>--user=</option> command line
 178         switch.</para></listitem>
 179       </varlistentry>
 180
 181       <varlistentry>
 182         <term><varname>WorkingDirectory=</varname></term>
 183
 184         <listitem><para>Selects the working directory for the process invoked in the container. Expects an absolute
 185         path in the container's file system namespace. This corresponds to the <option>--chdir=</option> command line
 186         switch.</para></listitem>
 187       </varlistentry>
 188
 189       <varlistentry>
 190         <term><varname>PivotRoot=</varname></term>
 191
 192         <listitem><para>Selects a directory to pivot to <filename>/</filename> inside the container when starting up.
 193         Takes a single path, or a pair of two paths separated by a colon. Both paths must be absolute, and are resolved
 194         in the container's file system namespace. This corresponds to the <option>--pivot-root=</option> command line
 195         switch.</para></listitem>
 196       </varlistentry>
 197
 198       <varlistentry>
 199         <term><varname>Capability=</varname></term>
 200         <term><varname>DropCapability=</varname></term>
 201
 202         <listitem><para>Takes a space-separated list of Linux process
 203         capabilities (see
 204         <citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
 205         for details). The <varname>Capability=</varname> setting
 206         specifies additional capabilities to pass on top of the
 207         default set of capabilities. The
 208         <varname>DropCapability=</varname> setting specifies
 209         capabilities to drop from the default set. These settings
 210         correspond to the <option>--capability=</option> and
 211         <option>--drop-capability=</option> command line
 212         switches. Note that <varname>Capability=</varname> is a
 213         privileged setting, and only takes effect in
 214         <filename>.nspawn</filename> files in
 215         <filename>/etc/systemd/nspawn/</filename> and
 216         <filename>/run/system/nspawn/</filename> (see above). On the
 217         other hand, <varname>DropCapability=</varname> takes effect in
 218         all cases.</para></listitem>
 219       </varlistentry>
 220
 221       <varlistentry>
 222         <term><varname>NoNewPrivileges=</varname></term>
 223
 224         <listitem><para>Takes a boolean argument that controls the <constant>PR_SET_NO_NEW_PRIVS</constant> flag for
 225         the container payload. This is equivalent to the
 226         <option>--no-new-privileges=</option> command line switch. See
 227         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 228         details.</para>
 229         </listitem>
 230       </varlistentry>
 231
 232       <varlistentry>
 233         <term><varname>KillSignal=</varname></term>
 234
 235         <listitem><para>Specify the process signal to send to the
 236         container's PID 1 when nspawn itself receives SIGTERM, in
 237         order to trigger an orderly shutdown of the container.
 238         Defaults to SIGRTMIN+3 if <option>Boot=</option> is used
 239         (on systemd-compatible init systems SIGRTMIN+3 triggers an
 240         orderly shutdown). For a list of valid signals, see
 241         <citerefentry project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem>
 242       </varlistentry>
 243
 244       <varlistentry>
 245         <term><varname>Personality=</varname></term>
 246
 247         <listitem><para>Configures the kernel personality for the
 248         container. This is equivalent to the
 249         <option>--personality=</option> switch.</para></listitem>
 250       </varlistentry>
 251
 252       <varlistentry>
 253         <term><varname>MachineID=</varname></term>
 254
 255         <listitem><para>Configures the 128-bit machine ID (UUID) to pass to
 256         the container. This is equivalent to the
 257         <option>--uuid=</option> command line switch. This option is
 258         privileged (see above). </para></listitem>
 259       </varlistentry>
 260
 261       <varlistentry>
 262         <term><varname>PrivateUsers=</varname></term>
 263
 264         <listitem><para>Configures support for usernamespacing. This is equivalent to the
 265         <option>--private-users=</option> command line switch, and takes the same options. This option is privileged
 266         (see above). This option is the default if the <filename>systemd-nspawn@.service</filename> template unit file
 267         is used.</para></listitem>
 268       </varlistentry>
 269
 270       <varlistentry>
 271         <term><varname>NotifyReady=</varname></term>
 272
 273         <listitem><para>Configures support for notifications from the container's init process.  This is equivalent to
 274         the <option>--notify-ready=</option> command line switch, and takes the same parameters. See
 275         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for details
 276         about the specific options supported.</para></listitem>
 277       </varlistentry>
 278
 279       <varlistentry>
 280         <term><varname>SystemCallFilter=</varname></term>
 281
 282         <listitem><para>Configures the system call filter applied to containers. This is equivalent to the
 283         <option>--system-call-filter=</option> command line switch, and takes the same list parameter. See
 284         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 285         details.</para></listitem>
 286       </varlistentry>
 287
 288       <varlistentry>
 289         <term><varname>LimitCPU=</varname></term>
 290         <term><varname>LimitFSIZE=</varname></term>
 291         <term><varname>LimitDATA=</varname></term>
 292         <term><varname>LimitSTACK=</varname></term>
 293         <term><varname>LimitCORE=</varname></term>
 294         <term><varname>LimitRSS=</varname></term>
 295         <term><varname>LimitNOFILE=</varname></term>
 296         <term><varname>LimitAS=</varname></term>
 297         <term><varname>LimitNPROC=</varname></term>
 298         <term><varname>LimitMEMLOCK=</varname></term>
 299         <term><varname>LimitLOCKS=</varname></term>
 300         <term><varname>LimitSIGPENDING=</varname></term>
 301         <term><varname>LimitMSGQUEUE=</varname></term>
 302         <term><varname>LimitNICE=</varname></term>
 303         <term><varname>LimitRTPRIO=</varname></term>
 304         <term><varname>LimitRTTIME=</varname></term>
 305
 306         <listitem><para>Configures various types of resource limits applied to containers. This is equivalent to the
 307         <option>--rlimit=</option> command line switch, and takes the same arguments. See
 308         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 309         details.</para></listitem>
 310       </varlistentry>
 311
 312       <varlistentry>
 313         <term><varname>OOMScoreAdjust=</varname></term>
 314
 315         <listitem><para>Configures the OOM score adjustment value. This is equivalent to the
 316         <option>--oom-score-adjust=</option> command line switch, and takes the same argument. See
 317         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 318         details.</para></listitem>
 319       </varlistentry>
 320
 321       <varlistentry>
 322         <term><varname>CPUAffinity=</varname></term>
 323
 324         <listitem><para>Configures the CPU affinity. This is equivalent to the <option>--cpu-affinity=</option> command
 325         line switch, and takes the same argument. See
 326         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 327         details.</para></listitem>
 328       </varlistentry>
 329
 330       <varlistentry>
 331         <term><varname>Hostname=</varname></term>
 332
 333         <listitem><para>Configures the kernel hostname set for the container. This is equivalent to the
 334         <option>--hostname=</option> command line switch, and takes the same argument. See
 335         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 336         details.</para></listitem>
 337       </varlistentry>
 338
 339       <varlistentry>
 340         <term><varname>ResolvConf=</varname></term>
 341
 342         <listitem><para>Configures how <filename>/etc/resolv.conf</filename> in the container shall be handled. This is
 343         equivalent to the <option>--resolv-conf=</option> command line switch, and takes the same argument. See
 344         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 345         details.</para></listitem>
 346       </varlistentry>
 347
 348       <varlistentry>
 349         <term><varname>Timezone=</varname></term>
 350
 351         <listitem><para>Configures how <filename>/etc/localtime</filename> in the container shall be handled. This is
 352         equivalent to the <option>--localtime=</option> command line switch, and takes the same argument. See
 353         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 354         details.</para></listitem>
 355       </varlistentry>
 356
 357       <varlistentry>
 358         <term><varname>LinkJournal=</varname></term>
 359
 360         <listitem><para>Configures how to link host and container journal setups. This is equivalent to the
 361         <option>--link-journal=</option> command line switch, and takes the same parameter. See
 362         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for
 363         details.</para></listitem>
 364       </varlistentry>
 365
 366     </variablelist>
 367   </refsect1>
 368
 369   <refsect1>
 370     <title>[Files] Section Options</title>
 371
 372     <para>Settings files may include a <literal>[Files]</literal>
 373     section, which carries various parameters configuring the file
 374     system of the container:</para>
 375
 376     <variablelist>
 377
 378       <varlistentry>
 379         <term><varname>ReadOnly=</varname></term>
 380
 381         <listitem><para>Takes a boolean argument, which defaults to off. If
 382         specified, the container will be run with a read-only file
 383         system. This setting corresponds to the
 384         <option>--read-only</option> command line
 385         switch.</para></listitem>
 386       </varlistentry>
 387
 388       <varlistentry>
 389         <term><varname>Volatile=</varname></term>
 390
 391         <listitem><para>Takes a boolean argument, or the special value
 392         <literal>state</literal>. This configures whether to run the
 393         container with volatile state and/or configuration. This
 394         option is equivalent to <option>--volatile=</option>, see
 395         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
 396         for details about the specific options
 397         supported.</para></listitem>
 398       </varlistentry>
 399
 400       <varlistentry>
 401         <term><varname>Bind=</varname></term>
 402         <term><varname>BindReadOnly=</varname></term>
 403
 404         <listitem><para>Adds a bind mount from the host into the
 405         container. Takes a single path, a pair of two paths separated
 406         by a colon, or a triplet of two paths plus an option string
 407         separated by colons. This option may be used multiple times to
 408         configure multiple bind mounts. This option is equivalent to
 409         the command line switches <option>--bind=</option> and
 410         <option>--bind-ro=</option>, see
 411         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
 412         for details about the specific options supported. This setting
 413         is privileged (see above).</para></listitem>
 414       </varlistentry>
 415
 416       <varlistentry>
 417         <term><varname>TemporaryFileSystem=</varname></term>
 418
 419         <listitem><para>Adds a <literal>tmpfs</literal> mount to the
 420         container. Takes a path or a pair of path and option string,
 421         separated by a colon. This option may be used multiple times to
 422         configure multiple <literal>tmpfs</literal> mounts. This
 423         option is equivalent to the command line switch
 424         <option>--tmpfs=</option>, see
 425         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
 426         for details about the specific options supported. This setting
 427         is privileged (see above).</para></listitem>
 428       </varlistentry>
 429
 430       <varlistentry>
 431         <term><varname>Overlay=</varname></term>
 432         <term><varname>OverlayReadOnly=</varname></term>
 433
 434         <listitem><para>Adds an overlay mount point. Takes a colon-separated list of paths.  This option may be used
 435         multiple times to configure multiple overlay mounts. This option is equivalent to the command line switches
 436         <option>--overlay=</option> and <option>--overlay-ro=</option>, see
 437         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry> for details
 438         about the specific options supported. This setting is privileged (see above).</para></listitem>
 439       </varlistentry>
 440
 441       <varlistentry>
 442         <term><varname>PrivateUsersChown=</varname></term>
 443
 444         <listitem><para>Configures whether the ownership of the files and directories in the container tree shall be
 445         adjusted to the UID/GID range used, if necessary and user namespacing is enabled. This is equivalent to the
 446         <option>--private-users-chown</option> command line switch. This option is privileged (see
 447         above). </para></listitem>
 448       </varlistentry>
 449
 450     </variablelist>
 451   </refsect1>
 452
 453   <refsect1>
 454     <title>[Network] Section Options</title>
 455
 456     <para>Settings files may include a <literal>[Network]</literal>
 457     section, which carries various parameters configuring the network
 458     connectivity of the container:</para>
 459
 460     <variablelist>
 461
 462       <varlistentry>
 463         <term><varname>Private=</varname></term>
 464
 465         <listitem><para>Takes a boolean argument, which defaults to off. If
 466         enabled, the container will run in its own network namespace
 467         and not share network interfaces and configuration with the
 468         host. This setting corresponds to the
 469         <option>--private-network</option> command line
 470         switch.</para></listitem>
 471       </varlistentry>
 472
 473       <varlistentry>
 474         <term><varname>VirtualEthernet=</varname></term>
 475
 476         <listitem><para>Takes a boolean argument. Configures whether to create a virtual Ethernet connection
 477         (<literal>veth</literal>) between host and the container. This setting implies
 478         <varname>Private=yes</varname>. This setting corresponds to the <option>--network-veth</option> command line
 479         switch. This option is privileged (see above). This option is the default if the
 480         <filename>systemd-nspawn@.service</filename> template unit file is used.</para></listitem>
 481       </varlistentry>
 482
 483       <varlistentry>
 484         <term><varname>VirtualEthernetExtra=</varname></term>
 485
 486         <listitem><para>Takes a colon-separated pair of interface
 487         names. Configures an additional virtual Ethernet connection
 488         (<literal>veth</literal>) between host and the container. The
 489         first specified name is the interface name on the host, the
 490         second the interface name in the container. The latter may be
 491         omitted in which case it is set to the same name as the host
 492         side interface. This setting implies
 493         <varname>Private=yes</varname>. This setting corresponds to
 494         the <option>--network-veth-extra=</option> command line
 495         switch, and maybe be used multiple times. It is independent of
 496         <varname>VirtualEthernet=</varname>. This option is privileged
 497         (see above).</para></listitem>
 498       </varlistentry>
 499
 500       <varlistentry>
 501         <term><varname>Interface=</varname></term>
 502
 503         <listitem><para>Takes a space-separated list of interfaces to
 504         add to the container. This option corresponds to the
 505         <option>--network-interface=</option> command line switch and
 506         implies <varname>Private=yes</varname>. This option is
 507         privileged (see above).</para></listitem>
 508       </varlistentry>
 509
 510       <varlistentry>
 511         <term><varname>MACVLAN=</varname></term>
 512         <term><varname>IPVLAN=</varname></term>
 513
 514         <listitem><para>Takes a space-separated list of interfaces to
 515         add MACLVAN or IPVLAN interfaces to, which are then added to
 516         the container. These options correspond to the
 517         <option>--network-macvlan=</option> and
 518         <option>--network-ipvlan=</option> command line switches and
 519         imply <varname>Private=yes</varname>. These options are
 520         privileged (see above).</para></listitem>
 521       </varlistentry>
 522
 523       <varlistentry>
 524         <term><varname>Bridge=</varname></term>
 525
 526         <listitem><para>Takes an interface name. This setting implies
 527         <varname>VirtualEthernet=yes</varname> and
 528         <varname>Private=yes</varname> and has the effect that the
 529         host side of the created virtual Ethernet link is connected to
 530         the specified bridge interface. This option corresponds to the
 531         <option>--network-bridge=</option> command line switch. This
 532         option is privileged (see above).</para></listitem>
 533       </varlistentry>
 534
 535       <varlistentry>
 536         <term><varname>Zone=</varname></term>
 537
 538         <listitem><para>Takes a network zone name. This setting implies <varname>VirtualEthernet=yes</varname> and
 539         <varname>Private=yes</varname> and has the effect that the host side of the created virtual Ethernet link is
 540         connected to an automatically managed bridge interface named after the passed argument, prefixed with
 541         <literal>vz-</literal>. This option corresponds to the <option>--network-zone=</option> command line
 542         switch. This option is privileged (see above).</para></listitem>
 543       </varlistentry>
 544
 545       <varlistentry>
 546         <term><varname>Port=</varname></term>
 547
 548         <listitem><para>Exposes a TCP or UDP port of the container on
 549         the host. This option corresponds to the
 550         <option>--port=</option> command line switch, see
 551         <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>
 552         for the precise syntax of the argument this option takes. This
 553         option is privileged (see above).</para></listitem>
 554       </varlistentry>
 555     </variablelist>
 556   </refsect1>
 557
 558   <refsect1>
 559     <title>See Also</title>
 560     <para>
 561       <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 562       <citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
 563       <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
 564     </para>
 565   </refsect1>
 566
 567 </refentry>