man/systemd.nspawn.xml

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