2011-03-16 03:51:41 +08:00
|
|
|
|
<?xml version='1.0'?> <!--*-nxml-*-->
|
|
|
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
|
|
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
|
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
|
This file is part of systemd.
|
|
|
|
|
|
|
|
|
|
|
|
Copyright 2010 Lennart Poettering
|
|
|
|
|
|
|
|
|
|
|
|
systemd is free software; you can redistribute it and/or modify it
|
2012-04-12 06:20:58 +08:00
|
|
|
|
under the terms of the GNU Lesser General Public License as published by
|
|
|
|
|
|
the Free Software Foundation; either version 2.1 of the License, or
|
2011-03-16 03:51:41 +08:00
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
|
|
|
|
systemd is distributed in the hope that it will be useful, but
|
|
|
|
|
|
WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
2012-04-12 06:20:58 +08:00
|
|
|
|
Lesser General Public License for more details.
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
2012-04-12 06:20:58 +08:00
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
2011-03-16 03:51:41 +08:00
|
|
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
|
-->
|
|
|
|
|
|
|
2014-02-14 03:33:51 +08:00
|
|
|
|
<refentry id="systemd-nspawn"
|
|
|
|
|
|
xmlns:xi="http://www.w3.org/2001/XInclude">
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<refentryinfo>
|
|
|
|
|
|
<title>systemd-nspawn</title>
|
|
|
|
|
|
<productname>systemd</productname>
|
|
|
|
|
|
|
|
|
|
|
|
<authorgroup>
|
|
|
|
|
|
<author>
|
|
|
|
|
|
<contrib>Developer</contrib>
|
|
|
|
|
|
<firstname>Lennart</firstname>
|
|
|
|
|
|
<surname>Poettering</surname>
|
|
|
|
|
|
<email>lennart@poettering.net</email>
|
|
|
|
|
|
</author>
|
|
|
|
|
|
</authorgroup>
|
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
|
|
<refentrytitle>systemd-nspawn</refentrytitle>
|
|
|
|
|
|
<manvolnum>1</manvolnum>
|
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
|
|
<refname>systemd-nspawn</refname>
|
|
|
|
|
|
<refpurpose>Spawn a namespace container for debugging, testing and building</refpurpose>
|
|
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
|
|
<cmdsynopsis>
|
2013-01-13 05:55:04 +08:00
|
|
|
|
<command>systemd-nspawn</command>
|
|
|
|
|
|
<arg choice="opt" rep="repeat">OPTIONS</arg>
|
2013-02-28 11:25:40 +08:00
|
|
|
|
<arg choice="opt"><replaceable>COMMAND</replaceable>
|
|
|
|
|
|
<arg choice="opt" rep="repeat">ARGS</arg>
|
|
|
|
|
|
</arg>
|
|
|
|
|
|
</cmdsynopsis>
|
|
|
|
|
|
<cmdsynopsis>
|
|
|
|
|
|
<command>systemd-nspawn</command>
|
|
|
|
|
|
<arg choice="plain">-b</arg>
|
|
|
|
|
|
<arg choice="opt" rep="repeat">OPTIONS</arg>
|
2013-01-13 05:55:04 +08:00
|
|
|
|
<arg choice="opt" rep="repeat">ARGS</arg>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
</cmdsynopsis>
|
|
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
|
|
|
|
<para><command>systemd-nspawn</command> may be used to
|
|
|
|
|
|
run a command or OS in a light-weight namespace
|
|
|
|
|
|
container. In many ways it is similar to
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2011-03-16 03:51:41 +08:00
|
|
|
|
but more powerful since it fully virtualizes the file
|
2011-06-18 21:40:20 +08:00
|
|
|
|
system hierarchy, as well as the process tree, the
|
2011-03-16 03:51:41 +08:00
|
|
|
|
various IPC subsystems and the host and domain
|
|
|
|
|
|
name.</para>
|
|
|
|
|
|
|
|
|
|
|
|
<para><command>systemd-nspawn</command> limits access
|
|
|
|
|
|
to various kernel interfaces in the container to
|
|
|
|
|
|
read-only, such as <filename>/sys</filename>,
|
|
|
|
|
|
<filename>/proc/sys</filename> or
|
2011-08-02 10:55:10 +08:00
|
|
|
|
<filename>/sys/fs/selinux</filename>. Network
|
|
|
|
|
|
interfaces and the system clock may not be changed
|
|
|
|
|
|
from within the container. Device nodes may not be
|
|
|
|
|
|
created. The host system cannot be rebooted and kernel
|
|
|
|
|
|
modules may not be loaded from within the
|
|
|
|
|
|
container.</para>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<para>Note that even though these security precautions
|
|
|
|
|
|
are taken <command>systemd-nspawn</command> is not
|
|
|
|
|
|
suitable for secure container setups. Many of the
|
|
|
|
|
|
security features may be circumvented and are hence
|
|
|
|
|
|
primarily useful to avoid accidental changes to the
|
|
|
|
|
|
host system from the container. The intended use of
|
|
|
|
|
|
this program is debugging and testing as well as
|
|
|
|
|
|
building of packages, distributions and software
|
|
|
|
|
|
involved with boot and systems management.</para>
|
|
|
|
|
|
|
|
|
|
|
|
<para>In contrast to
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>systemd-nspawn</command>
|
2013-08-20 04:00:13 +08:00
|
|
|
|
may be used to boot full Linux-based operating systems
|
|
|
|
|
|
in a container.</para>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<para>Use a tool like
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='die-net'><refentrytitle>yum</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
|
<citerefentry project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2013-01-29 08:44:33 +08:00
|
|
|
|
or
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='arch'><refentrytitle>pacman</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
to set up an OS directory tree suitable as file system
|
2012-04-24 19:14:27 +08:00
|
|
|
|
hierarchy for <command>systemd-nspawn</command>
|
|
|
|
|
|
containers.</para>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<para>Note that <command>systemd-nspawn</command> will
|
|
|
|
|
|
mount file systems private to the container to
|
|
|
|
|
|
<filename>/dev</filename>,
|
2011-03-25 12:07:20 +08:00
|
|
|
|
<filename>/run</filename> and similar. These will
|
2011-03-16 03:51:41 +08:00
|
|
|
|
not be visible outside of the container, and their
|
|
|
|
|
|
contents will be lost when the container exits.</para>
|
|
|
|
|
|
|
|
|
|
|
|
<para>Note that running two
|
|
|
|
|
|
<command>systemd-nspawn</command> containers from the
|
|
|
|
|
|
same directory tree will not make processes in them
|
2011-06-18 21:40:20 +08:00
|
|
|
|
see each other. The PID namespace separation of the
|
2011-03-16 03:51:41 +08:00
|
|
|
|
two containers is complete and the containers will
|
|
|
|
|
|
share very few runtime objects except for the
|
2013-10-31 08:25:44 +08:00
|
|
|
|
underlying file system. Use
|
|
|
|
|
|
<citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
|
|
|
|
|
|
<command>login</command> command to request an
|
|
|
|
|
|
additional login prompt in a running container.</para>
|
2012-06-29 00:58:56 +08:00
|
|
|
|
|
|
|
|
|
|
<para><command>systemd-nspawn</command> implements the
|
|
|
|
|
|
<ulink
|
|
|
|
|
|
url="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container
|
|
|
|
|
|
Interface</ulink> specification.</para>
|
2013-05-07 03:04:31 +08:00
|
|
|
|
|
|
|
|
|
|
<para>As a safety check
|
|
|
|
|
|
<command>systemd-nspawn</command> will verify the
|
2014-06-14 01:45:52 +08:00
|
|
|
|
existence of <filename>/usr/lib/os-release</filename>
|
|
|
|
|
|
or <filename>/etc/os-release</filename> in the
|
|
|
|
|
|
container tree before starting the container (see
|
2013-05-07 03:04:31 +08:00
|
|
|
|
<citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry>). It
|
|
|
|
|
|
might be necessary to add this file to the container
|
|
|
|
|
|
tree manually if the OS of the container is too old to
|
|
|
|
|
|
contain this file out-of-the-box.</para>
|
2013-05-10 06:14:12 +08:00
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
2011-03-16 03:51:41 +08:00
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Options</title>
|
|
|
|
|
|
|
2013-02-28 11:25:40 +08:00
|
|
|
|
<para>If option <option>-b</option> is specified, the
|
|
|
|
|
|
arguments are used as arguments for the init
|
|
|
|
|
|
binary. Otherwise, <replaceable>COMMAND</replaceable>
|
|
|
|
|
|
specifies the program to launch in the container, and
|
|
|
|
|
|
the remaining arguments are used as arguments for this
|
|
|
|
|
|
program. If <option>-b</option> is not used and no
|
|
|
|
|
|
arguments are specifed, a shell is launched in the
|
|
|
|
|
|
container.</para>
|
|
|
|
|
|
|
|
|
|
|
|
<para>The following options are understood:</para>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
|
|
<varlistentry>
|
2011-08-20 06:20:41 +08:00
|
|
|
|
<term><option>-D</option></term>
|
2013-02-13 17:39:22 +08:00
|
|
|
|
<term><option>--directory=</option></term>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<listitem><para>Directory to use as
|
2014-03-11 03:35:52 +08:00
|
|
|
|
file system root for the container. If
|
|
|
|
|
|
neither <option>--directory=</option>
|
|
|
|
|
|
nor <option>--image=</option> are
|
|
|
|
|
|
specified, the current directory will
|
|
|
|
|
|
be used. May not be specified together with
|
|
|
|
|
|
<option>--image=</option>.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-i</option></term>
|
|
|
|
|
|
<term><option>--image=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Disk image to mount
|
|
|
|
|
|
the root directory for the container
|
|
|
|
|
|
from. Takes a path to a regular file
|
|
|
|
|
|
or to a block device node. The file or
|
|
|
|
|
|
block device must contain a GUID
|
|
|
|
|
|
Partition Table with a root partition
|
|
|
|
|
|
which is mounted as the root directory
|
|
|
|
|
|
of the container. Optionally, it may
|
|
|
|
|
|
contain a home and/or a server data
|
|
|
|
|
|
partition which are mounted to the
|
|
|
|
|
|
appropriate places in the
|
|
|
|
|
|
container. All these partitions must
|
|
|
|
|
|
be identified by the partition types
|
|
|
|
|
|
defined by the <ulink
|
|
|
|
|
|
url="http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/">Discoverable
|
|
|
|
|
|
Partitions Specification</ulink>. Any
|
|
|
|
|
|
other partitions, such as foreign
|
|
|
|
|
|
partitions, swap partitions or EFI
|
|
|
|
|
|
system partitions are not mounted. May
|
|
|
|
|
|
not be specified together with
|
|
|
|
|
|
<option>--directory=</option>.</para></listitem>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2012-04-22 19:37:24 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-b</option></term>
|
2013-02-13 17:39:22 +08:00
|
|
|
|
<term><option>--boot</option></term>
|
2012-04-22 19:37:24 +08:00
|
|
|
|
|
|
|
|
|
|
<listitem><para>Automatically search
|
|
|
|
|
|
for an init binary and invoke it
|
|
|
|
|
|
instead of a shell or a user supplied
|
2014-02-10 22:36:32 +08:00
|
|
|
|
program. If this option is used,
|
|
|
|
|
|
arguments specified on the command
|
|
|
|
|
|
line are used as arguments for the
|
|
|
|
|
|
init binary. This option may not be
|
|
|
|
|
|
combined with
|
|
|
|
|
|
<option>--share-system</option>.
|
2013-02-28 11:25:40 +08:00
|
|
|
|
</para></listitem>
|
2012-04-22 19:37:24 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2011-06-29 20:22:46 +08:00
|
|
|
|
<varlistentry>
|
2011-08-02 10:55:10 +08:00
|
|
|
|
<term><option>-u</option></term>
|
2013-02-13 17:39:22 +08:00
|
|
|
|
<term><option>--user=</option></term>
|
2011-06-29 20:22:46 +08:00
|
|
|
|
|
2014-03-12 03:20:54 +08:00
|
|
|
|
<listitem><para>After transitioning
|
|
|
|
|
|
into the container, change to the
|
2014-05-04 01:15:24 +08:00
|
|
|
|
specified user-defined in the
|
2014-03-12 03:20:54 +08:00
|
|
|
|
container's user database. Like all
|
|
|
|
|
|
other systemd-nspawn features, this is
|
|
|
|
|
|
not a security feature and provides
|
|
|
|
|
|
protection against accidental
|
|
|
|
|
|
destructive operations
|
|
|
|
|
|
only.</para></listitem>
|
2011-06-29 20:22:46 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2013-04-16 10:36:06 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-M</option></term>
|
|
|
|
|
|
<term><option>--machine=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the machine name
|
|
|
|
|
|
for this container. This name may be
|
|
|
|
|
|
used to identify this container on the
|
|
|
|
|
|
host, and is used to initialize the
|
|
|
|
|
|
container's hostname (which the
|
|
|
|
|
|
container can choose to override,
|
2013-09-13 03:12:49 +08:00
|
|
|
|
however). If not specified, the last
|
2013-04-16 10:36:06 +08:00
|
|
|
|
component of the root directory of the
|
|
|
|
|
|
container is used.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2012-04-22 20:48:21 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--uuid=</option></term>
|
|
|
|
|
|
|
2013-06-28 03:51:44 +08:00
|
|
|
|
<listitem><para>Set the specified UUID
|
2012-04-22 20:48:21 +08:00
|
|
|
|
for the container. The init system
|
|
|
|
|
|
will initialize
|
|
|
|
|
|
<filename>/etc/machine-id</filename>
|
|
|
|
|
|
from this if this file is not set yet.
|
|
|
|
|
|
</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-14 01:47:20 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--slice=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Make the container
|
|
|
|
|
|
part of the specified slice, instead
|
|
|
|
|
|
of the default
|
|
|
|
|
|
<filename>machine.slice</filename>.</para>
|
|
|
|
|
|
</listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2011-08-02 10:49:37 +08:00
|
|
|
|
<varlistentry>
|
2011-08-02 11:24:58 +08:00
|
|
|
|
<term><option>--private-network</option></term>
|
2011-08-02 10:49:37 +08:00
|
|
|
|
|
2014-02-14 01:47:20 +08:00
|
|
|
|
<listitem><para>Disconnect networking
|
|
|
|
|
|
of the container from the host. This
|
|
|
|
|
|
makes all network interfaces
|
|
|
|
|
|
unavailable in the container, with the
|
|
|
|
|
|
exception of the loopback device and
|
|
|
|
|
|
those specified with
|
|
|
|
|
|
<option>--network-interface=</option>
|
2014-02-17 04:12:47 +08:00
|
|
|
|
and configured with
|
2014-02-14 01:47:20 +08:00
|
|
|
|
<option>--network-veth</option>. If
|
2014-02-17 10:37:13 +08:00
|
|
|
|
this option is specified, the
|
2014-02-13 21:07:59 +08:00
|
|
|
|
CAP_NET_ADMIN capability will be added
|
|
|
|
|
|
to the set of capabilities the
|
|
|
|
|
|
container retains. The latter may be
|
|
|
|
|
|
disabled by using
|
|
|
|
|
|
<option>--drop-capability=</option>.</para></listitem>
|
2011-08-02 10:49:37 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-13 10:27:39 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--network-interface=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Assign the specified
|
|
|
|
|
|
network interface to the
|
2014-02-25 09:27:39 +08:00
|
|
|
|
container. This will remove the
|
2014-02-13 10:27:39 +08:00
|
|
|
|
specified interface from the calling
|
|
|
|
|
|
namespace and place it in the
|
|
|
|
|
|
container. When the container
|
2014-02-17 10:37:13 +08:00
|
|
|
|
terminates, it is moved back to the
|
2014-02-13 21:07:59 +08:00
|
|
|
|
host namespace. Note that
|
|
|
|
|
|
<option>--network-interface=</option>
|
|
|
|
|
|
implies
|
|
|
|
|
|
<option>--private-network</option>. This
|
|
|
|
|
|
option may be used more than once to
|
|
|
|
|
|
add multiple network interfaces to the
|
|
|
|
|
|
container.</para></listitem>
|
2014-02-13 10:27:39 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-25 09:27:39 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--network-macvlan=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Create a
|
|
|
|
|
|
<literal>macvlan</literal> interface
|
|
|
|
|
|
of the specified Ethernet network
|
|
|
|
|
|
interface and add it to the
|
|
|
|
|
|
container. A
|
|
|
|
|
|
<literal>macvlan</literal> interface
|
|
|
|
|
|
is a virtual interface that adds a
|
|
|
|
|
|
second MAC address to an existing
|
|
|
|
|
|
physical Ethernet link. The interface
|
|
|
|
|
|
in the container will be named after
|
|
|
|
|
|
the interface on the host, prefixed
|
|
|
|
|
|
with <literal>mv-</literal>. Note that
|
|
|
|
|
|
<option>--network-macvlan=</option>
|
|
|
|
|
|
implies
|
|
|
|
|
|
<option>--private-network</option>. This
|
|
|
|
|
|
option may be used more than once to
|
|
|
|
|
|
add multiple network interfaces to the
|
|
|
|
|
|
container.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2012-04-25 21:11:20 +08:00
|
|
|
|
<varlistentry>
|
2014-02-14 01:47:20 +08:00
|
|
|
|
<term><option>--network-veth</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Create a virtual
|
2014-02-25 09:27:39 +08:00
|
|
|
|
Ethernet link
|
|
|
|
|
|
(<literal>veth</literal>) between host
|
|
|
|
|
|
and container. The host side of the
|
2014-02-17 10:37:18 +08:00
|
|
|
|
Ethernet link will be available as a
|
2014-02-14 01:47:20 +08:00
|
|
|
|
network interface named after the
|
|
|
|
|
|
container's name (as specified with
|
|
|
|
|
|
<option>--machine=</option>), prefixed
|
|
|
|
|
|
with <literal>ve-</literal>. The
|
2014-05-08 07:28:44 +08:00
|
|
|
|
container side of the Ethernet
|
2014-02-14 01:47:20 +08:00
|
|
|
|
link will be named
|
|
|
|
|
|
<literal>host0</literal>. Note that
|
|
|
|
|
|
<option>--network-veth</option>
|
|
|
|
|
|
implies
|
|
|
|
|
|
<option>--private-network</option>.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
2012-04-25 21:11:20 +08:00
|
|
|
|
|
2014-02-17 04:12:47 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--network-bridge=</option></term>
|
|
|
|
|
|
|
2014-02-21 11:02:12 +08:00
|
|
|
|
<listitem><para>Adds the host side of
|
|
|
|
|
|
the Ethernet link created with
|
|
|
|
|
|
<option>--network-veth</option> to the
|
|
|
|
|
|
specified bridge. Note that
|
|
|
|
|
|
<option>--network-bridge=</option>
|
2014-02-17 04:12:47 +08:00
|
|
|
|
implies
|
2014-02-21 11:02:12 +08:00
|
|
|
|
<option>--network-veth</option>. If
|
2014-05-08 07:28:45 +08:00
|
|
|
|
this option is used, the host side of
|
2014-02-21 11:02:12 +08:00
|
|
|
|
the Ethernet link will use the
|
|
|
|
|
|
<literal>vb-</literal> prefix instead
|
|
|
|
|
|
of <literal>ve-</literal>.</para></listitem>
|
2014-02-17 04:12:47 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-14 01:47:20 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-Z</option></term>
|
|
|
|
|
|
<term><option>--selinux-context=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the SELinux
|
|
|
|
|
|
security context to be used to label
|
|
|
|
|
|
processes in the container.</para>
|
|
|
|
|
|
</listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-L</option></term>
|
|
|
|
|
|
<term><option>--selinux-apifs-context=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Sets the SELinux security
|
|
|
|
|
|
context to be used to label files in
|
|
|
|
|
|
the virtual API file systems in the
|
|
|
|
|
|
container.</para>
|
|
|
|
|
|
</listitem>
|
2012-04-25 21:11:20 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2012-06-28 19:44:39 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--capability=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>List one or more
|
|
|
|
|
|
additional capabilities to grant the
|
2013-06-28 03:51:44 +08:00
|
|
|
|
container. Takes a comma-separated
|
2012-06-28 19:44:39 +08:00
|
|
|
|
list of capability names, see
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
2012-06-28 19:44:39 +08:00
|
|
|
|
for more information. Note that the
|
2013-01-19 01:13:01 +08:00
|
|
|
|
following capabilities will be granted
|
|
|
|
|
|
in any way: CAP_CHOWN,
|
2012-06-28 19:44:39 +08:00
|
|
|
|
CAP_DAC_OVERRIDE, CAP_DAC_READ_SEARCH,
|
|
|
|
|
|
CAP_FOWNER, CAP_FSETID, CAP_IPC_OWNER,
|
|
|
|
|
|
CAP_KILL, CAP_LEASE,
|
|
|
|
|
|
CAP_LINUX_IMMUTABLE,
|
|
|
|
|
|
CAP_NET_BIND_SERVICE,
|
|
|
|
|
|
CAP_NET_BROADCAST, CAP_NET_RAW,
|
|
|
|
|
|
CAP_SETGID, CAP_SETFCAP, CAP_SETPCAP,
|
|
|
|
|
|
CAP_SETUID, CAP_SYS_ADMIN,
|
|
|
|
|
|
CAP_SYS_CHROOT, CAP_SYS_NICE,
|
|
|
|
|
|
CAP_SYS_PTRACE, CAP_SYS_TTY_CONFIG,
|
2013-01-19 01:13:01 +08:00
|
|
|
|
CAP_SYS_RESOURCE, CAP_SYS_BOOT,
|
2014-02-13 21:07:59 +08:00
|
|
|
|
CAP_AUDIT_WRITE,
|
|
|
|
|
|
CAP_AUDIT_CONTROL. Also CAP_NET_ADMIN
|
|
|
|
|
|
is retained if
|
|
|
|
|
|
<option>--private-network</option> is
|
|
|
|
|
|
specified. If the special value
|
2014-02-17 10:37:13 +08:00
|
|
|
|
<literal>all</literal> is passed, all
|
2014-02-13 09:45:11 +08:00
|
|
|
|
capabilities are
|
|
|
|
|
|
retained.</para></listitem>
|
2012-06-28 19:44:39 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2013-11-21 05:10:42 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--drop-capability=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Specify one or more
|
|
|
|
|
|
additional capabilities to drop for
|
|
|
|
|
|
the container. This allows running the
|
|
|
|
|
|
container with fewer capabilities than
|
|
|
|
|
|
the default (see above).</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2012-07-19 08:02:39 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--link-journal=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Control whether the
|
|
|
|
|
|
container's journal shall be made
|
2013-09-13 03:12:49 +08:00
|
|
|
|
visible to the host system. If enabled,
|
2012-07-19 08:02:39 +08:00
|
|
|
|
allows viewing the container's journal
|
|
|
|
|
|
files from the host (but not vice
|
|
|
|
|
|
versa). Takes one of
|
|
|
|
|
|
<literal>no</literal>,
|
|
|
|
|
|
<literal>host</literal>,
|
|
|
|
|
|
<literal>guest</literal>,
|
|
|
|
|
|
<literal>auto</literal>. If
|
2012-10-02 16:58:31 +08:00
|
|
|
|
<literal>no</literal>, the journal is
|
|
|
|
|
|
not linked. If <literal>host</literal>,
|
2012-07-19 08:02:39 +08:00
|
|
|
|
the journal files are stored on the
|
2012-10-02 16:58:31 +08:00
|
|
|
|
host file system (beneath
|
2013-02-14 11:46:37 +08:00
|
|
|
|
<filename>/var/log/journal/<replaceable>machine-id</replaceable></filename>)
|
2012-10-02 16:58:31 +08:00
|
|
|
|
and the subdirectory is bind-mounted
|
2012-07-19 08:02:39 +08:00
|
|
|
|
into the container at the same
|
2012-10-02 16:58:31 +08:00
|
|
|
|
location. If <literal>guest</literal>,
|
2012-07-19 08:02:39 +08:00
|
|
|
|
the journal files are stored on the
|
2012-10-02 16:58:31 +08:00
|
|
|
|
guest file system (beneath
|
2013-02-14 11:46:37 +08:00
|
|
|
|
<filename>/var/log/journal/<replaceable>machine-id</replaceable></filename>)
|
2012-10-02 16:58:31 +08:00
|
|
|
|
and the subdirectory is symlinked into the host
|
2012-07-19 08:02:39 +08:00
|
|
|
|
at the same location. If
|
2012-10-02 16:58:31 +08:00
|
|
|
|
<literal>auto</literal> (the default),
|
|
|
|
|
|
and the right subdirectory of
|
2012-07-19 08:02:39 +08:00
|
|
|
|
<filename>/var/log/journal</filename>
|
2012-10-02 16:58:31 +08:00
|
|
|
|
exists, it will be bind mounted
|
|
|
|
|
|
into the container. If the
|
2013-08-25 15:01:45 +08:00
|
|
|
|
subdirectory does not exist, no
|
2012-10-02 16:58:31 +08:00
|
|
|
|
linking is performed. Effectively,
|
|
|
|
|
|
booting a container once with
|
2012-07-19 08:02:39 +08:00
|
|
|
|
<literal>guest</literal> or
|
|
|
|
|
|
<literal>host</literal> will link the
|
2012-10-02 16:58:31 +08:00
|
|
|
|
journal persistently if further on
|
2012-07-19 08:02:39 +08:00
|
|
|
|
the default of <literal>auto</literal>
|
|
|
|
|
|
is used.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-j</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Equivalent to
|
|
|
|
|
|
<option>--link-journal=guest</option>.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
2013-02-26 01:21:13 +08:00
|
|
|
|
|
2014-02-14 01:47:20 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--read-only</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Mount the root file
|
|
|
|
|
|
system read-only for the
|
|
|
|
|
|
container.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2013-02-26 01:21:13 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--bind=</option></term>
|
|
|
|
|
|
<term><option>--bind-ro=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Bind mount a file or
|
|
|
|
|
|
directory from the host into the
|
|
|
|
|
|
container. Either takes a path
|
|
|
|
|
|
argument -- in which case the
|
|
|
|
|
|
specified path will be mounted from
|
|
|
|
|
|
the host to the same path in the
|
|
|
|
|
|
container --, or a colon-separated
|
|
|
|
|
|
pair of paths -- in which case the
|
|
|
|
|
|
first specified path is the source in
|
|
|
|
|
|
the host, and the second path is the
|
|
|
|
|
|
destination in the container. The
|
|
|
|
|
|
<option>--bind-ro=</option> option
|
|
|
|
|
|
creates read-only bind
|
2014-02-21 11:02:12 +08:00
|
|
|
|
mounts.</para></listitem>
|
2013-02-26 01:21:13 +08:00
|
|
|
|
</varlistentry>
|
2013-12-13 23:37:16 +08:00
|
|
|
|
|
2014-06-11 06:44:30 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--tmpfs=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Mount a tmpfs file
|
|
|
|
|
|
system into the container. Takes a
|
|
|
|
|
|
single absolute path argument that
|
|
|
|
|
|
specifies where to mount the tmpfs
|
|
|
|
|
|
instance to (in which case the
|
|
|
|
|
|
directory access mode will be chosen
|
|
|
|
|
|
as 0755, owned by root/root), or
|
|
|
|
|
|
optionally a colon-separated pair of
|
|
|
|
|
|
path and mount option string, that is
|
|
|
|
|
|
used for mounting (in which case the
|
|
|
|
|
|
kernel default for access mode and
|
|
|
|
|
|
owner will be chosen, unless otherwise
|
|
|
|
|
|
specified). This option is
|
|
|
|
|
|
particularly useful for mounting
|
|
|
|
|
|
directories such as
|
|
|
|
|
|
<filename>/var</filename> as tmpfs, to
|
|
|
|
|
|
allow state-less systems, in
|
|
|
|
|
|
particular when combined with
|
|
|
|
|
|
<option>--read-only</option>.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2013-12-13 23:37:16 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--setenv=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Specifies an
|
|
|
|
|
|
environment variable assignment to
|
|
|
|
|
|
pass to the init process in the
|
|
|
|
|
|
container, in the format
|
|
|
|
|
|
<literal>NAME=VALUE</literal>. This
|
|
|
|
|
|
may be used to override the default
|
|
|
|
|
|
variables or to set additional
|
|
|
|
|
|
variables. This parameter may be used
|
|
|
|
|
|
more than once.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-10 20:15:42 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--share-system</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Allows the container
|
|
|
|
|
|
to share certain system facilities
|
|
|
|
|
|
with the host. More specifically, this
|
|
|
|
|
|
turns off PID namespacing, UTS
|
|
|
|
|
|
namespacing and IPC namespacing, and
|
|
|
|
|
|
thus allows the guest to see and
|
|
|
|
|
|
interact more easily with processes
|
|
|
|
|
|
outside of the container. Note that
|
|
|
|
|
|
using this option makes it impossible
|
2014-02-10 22:36:32 +08:00
|
|
|
|
to start up a full Operating System in
|
|
|
|
|
|
the container, as an init system
|
|
|
|
|
|
cannot operate in this mode. It is
|
|
|
|
|
|
only useful to run specific programs
|
|
|
|
|
|
or applications this way, without
|
|
|
|
|
|
involving an init system in the
|
|
|
|
|
|
container. This option implies
|
|
|
|
|
|
<option>--register=no</option>. This
|
|
|
|
|
|
option may not be combined with
|
|
|
|
|
|
<option>--boot</option>.</para></listitem>
|
2014-02-10 20:15:42 +08:00
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-10 22:36:32 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--register=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Controls whether the
|
|
|
|
|
|
container is registered with
|
|
|
|
|
|
<citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Takes
|
|
|
|
|
|
a boolean argument, defaults to
|
|
|
|
|
|
<literal>yes</literal>. This option
|
|
|
|
|
|
should be enabled when the container
|
|
|
|
|
|
runs a full Operating System (more
|
|
|
|
|
|
specifically: an init system), and is
|
2014-02-12 00:15:38 +08:00
|
|
|
|
useful to ensure that the container is
|
|
|
|
|
|
accessible via
|
2014-02-10 22:36:32 +08:00
|
|
|
|
<citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
|
|
|
|
|
and shown by tools such as
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>. If
|
2014-02-10 22:36:32 +08:00
|
|
|
|
the container does not run an init
|
2014-02-17 10:37:13 +08:00
|
|
|
|
system, it is recommended to set this
|
2014-02-10 22:36:32 +08:00
|
|
|
|
option to <literal>no</literal>. Note
|
|
|
|
|
|
that <option>--share-system</option>
|
|
|
|
|
|
implies
|
|
|
|
|
|
<option>--register=no</option>.
|
|
|
|
|
|
</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
2014-02-12 00:15:38 +08:00
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--keep-unit</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Instead of creating a
|
|
|
|
|
|
transient scope unit to run the
|
|
|
|
|
|
container in, simply register the
|
|
|
|
|
|
service or scope unit
|
|
|
|
|
|
<command>systemd-nspawn</command> has
|
2014-02-17 10:37:18 +08:00
|
|
|
|
been invoked in with
|
2014-02-12 00:15:38 +08:00
|
|
|
|
<citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>. This
|
|
|
|
|
|
has no effect if
|
|
|
|
|
|
<option>--register=no</option> is
|
|
|
|
|
|
used. This switch should be used if
|
|
|
|
|
|
<command>systemd-nspawn</command> is
|
2014-02-17 10:37:18 +08:00
|
|
|
|
invoked from within a service unit,
|
2014-02-12 00:15:38 +08:00
|
|
|
|
and the service unit's sole purpose
|
|
|
|
|
|
is to run a single
|
|
|
|
|
|
<command>systemd-nspawn</command>
|
|
|
|
|
|
container. This option is not
|
|
|
|
|
|
available if run from a user
|
|
|
|
|
|
session.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-19 06:35:19 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--personality=</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Control the
|
|
|
|
|
|
architecture ("personality") reported
|
|
|
|
|
|
by
|
|
|
|
|
|
<citerefentry><refentrytitle>uname</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
|
|
|
|
|
in the container. Currently, only
|
|
|
|
|
|
<literal>x86</literal> and
|
|
|
|
|
|
<literal>x86-64</literal> are
|
|
|
|
|
|
supported. This is useful when running
|
2014-05-04 01:15:24 +08:00
|
|
|
|
a 32-bit container on a 64-bit
|
2014-05-08 07:28:45 +08:00
|
|
|
|
host. If this setting is not used,
|
2014-02-19 06:35:19 +08:00
|
|
|
|
the personality reported in the
|
|
|
|
|
|
container is the same as the one
|
|
|
|
|
|
reported on the
|
|
|
|
|
|
host.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
2014-02-14 03:33:51 +08:00
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>-q</option></term>
|
|
|
|
|
|
<term><option>--quiet</option></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Turns off any status
|
|
|
|
|
|
output by the tool itself. When this
|
|
|
|
|
|
switch is used, the only output
|
|
|
|
|
|
from nspawn will be the console output
|
|
|
|
|
|
of the container OS itself.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-07-04 18:17:12 +08:00
|
|
|
|
<varlistentry>
|
|
|
|
|
|
<term><option>--volatile</option><replaceable>=MODE</replaceable></term>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem><para>Boots the container in
|
|
|
|
|
|
volatile (ephemeral) mode. When no
|
|
|
|
|
|
mode parameter is passed or when mode
|
|
|
|
|
|
is specified as <literal>yes</literal>
|
|
|
|
|
|
full volatile mode is enabled. This
|
|
|
|
|
|
means the root directory is mounted as
|
|
|
|
|
|
mostly unpopulated
|
|
|
|
|
|
<literal>tmpfs</literal> instance, and
|
|
|
|
|
|
<filename>/usr</filename> from the OS
|
|
|
|
|
|
tree is mounted into it, read-only
|
|
|
|
|
|
(the system thus starts up with
|
|
|
|
|
|
read-only OS resources, but pristine
|
|
|
|
|
|
state and configuration, any changes
|
|
|
|
|
|
to the either are lost on
|
|
|
|
|
|
shutdown). When the mode parameter is
|
|
|
|
|
|
specified as <literal>state</literal>
|
|
|
|
|
|
the OS tree is mounted read-only, but
|
|
|
|
|
|
<filename>/var</filename> is mounted
|
|
|
|
|
|
as <literal>tmpfs</literal> instance
|
|
|
|
|
|
into it (the system thus starts up
|
|
|
|
|
|
with read-only OS resources and
|
|
|
|
|
|
configuration, but prestine state, any
|
|
|
|
|
|
changes to the latter are lost on
|
|
|
|
|
|
shutdown). When the mode parameter is
|
|
|
|
|
|
specified as <literal>no</literal>
|
|
|
|
|
|
(the default) the whole OS tree is made
|
|
|
|
|
|
available writable.</para>
|
|
|
|
|
|
|
|
|
|
|
|
<para>Note that setting this to
|
|
|
|
|
|
<literal>yes</literal> or
|
|
|
|
|
|
<literal>state</literal> will only
|
|
|
|
|
|
work correctly with operating systems
|
|
|
|
|
|
in the container that can boot up with
|
|
|
|
|
|
only <filename>/usr</filename>
|
|
|
|
|
|
mounted, and are able to populate
|
|
|
|
|
|
<filename>/var</filename>
|
|
|
|
|
|
automatically, as
|
|
|
|
|
|
needed.</para></listitem>
|
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
2014-02-14 03:33:51 +08:00
|
|
|
|
<xi:include href="standard-options.xml" xpointer="help" />
|
|
|
|
|
|
<xi:include href="standard-options.xml" xpointer="version" />
|
2011-03-16 03:51:41 +08:00
|
|
|
|
</variablelist>
|
|
|
|
|
|
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Example 1</title>
|
|
|
|
|
|
|
2013-01-19 01:22:55 +08:00
|
|
|
|
<programlisting># yum -y --releasever=19 --nogpg --installroot=/srv/mycontainer --disablerepo='*' --enablerepo=fedora install systemd passwd yum fedora-release vim-minimal
|
|
|
|
|
|
# systemd-nspawn -bD /srv/mycontainer</programlisting>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
2012-04-24 19:14:27 +08:00
|
|
|
|
<para>This installs a minimal Fedora distribution into
|
2013-05-03 12:55:20 +08:00
|
|
|
|
the directory <filename noindex='true'>/srv/mycontainer/</filename> and
|
2013-01-19 01:22:55 +08:00
|
|
|
|
then boots an OS in a namespace container in
|
|
|
|
|
|
it.</para>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Example 2</title>
|
|
|
|
|
|
|
2012-04-24 19:14:27 +08:00
|
|
|
|
<programlisting># debootstrap --arch=amd64 unstable ~/debian-tree/
|
|
|
|
|
|
# systemd-nspawn -D ~/debian-tree/</programlisting>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
|
2012-04-24 19:14:27 +08:00
|
|
|
|
<para>This installs a minimal Debian unstable
|
|
|
|
|
|
distribution into the directory
|
|
|
|
|
|
<filename>~/debian-tree/</filename> and then spawns a
|
|
|
|
|
|
shell in a namespace container in it.</para>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
2013-01-27 01:15:32 +08:00
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Example 3</title>
|
|
|
|
|
|
|
|
|
|
|
|
<programlisting># pacstrap -c -d ~/arch-tree/ base
|
|
|
|
|
|
# systemd-nspawn -bD ~/arch-tree/</programlisting>
|
|
|
|
|
|
|
|
|
|
|
|
<para>This installs a mimimal Arch Linux distribution into
|
|
|
|
|
|
the directory <filename>~/arch-tree/</filename> and then
|
|
|
|
|
|
boots an OS in a namespace container in it.</para>
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
2013-11-08 12:57:19 +08:00
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Example 4</title>
|
|
|
|
|
|
|
|
|
|
|
|
<programlisting># mv ~/arch-tree /var/lib/container/arch
|
|
|
|
|
|
# systemctl enable systemd-nspawn@arch.service
|
|
|
|
|
|
# systemctl start systemd-nspawn@arch.service</programlisting>
|
|
|
|
|
|
|
|
|
|
|
|
<para>This makes the Arch Linux container part of the
|
|
|
|
|
|
<filename>multi-user.target</filename> on the host.
|
|
|
|
|
|
</para>
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
2013-12-13 12:14:48 +08:00
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Example 5</title>
|
|
|
|
|
|
|
|
|
|
|
|
<programlisting># btrfs subvolume snapshot / /.tmp
|
|
|
|
|
|
# systemd-nspawn --private-network -D /.tmp -b</programlisting>
|
|
|
|
|
|
|
|
|
|
|
|
<para>This runs a copy of the host system in a
|
|
|
|
|
|
btrfs snapshot.</para>
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
2014-01-31 05:28:02 +08:00
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Example 6</title>
|
|
|
|
|
|
|
|
|
|
|
|
<programlisting># chcon system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 -R /srv/container
|
|
|
|
|
|
# systemd-nspawn -L system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 -Z system_u:system_r:svirt_lxc_net_t:s0:c0,c1 -D /srv/container /bin/sh</programlisting>
|
|
|
|
|
|
|
2014-02-10 19:32:03 +08:00
|
|
|
|
<para>This runs a container with SELinux sandbox security contexts.</para>
|
2014-01-31 05:28:02 +08:00
|
|
|
|
</refsect1>
|
2013-12-13 12:14:48 +08:00
|
|
|
|
|
2011-03-16 03:51:41 +08:00
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>Exit status</title>
|
|
|
|
|
|
|
|
|
|
|
|
<para>The exit code of the program executed in the
|
|
|
|
|
|
container is returned.</para>
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
<para>
|
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 06:25:54 +08:00
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
|
|
|
|
<citerefentry project='die-net'><refentrytitle>yum</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
|
<citerefentry project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
|
<citerefentry project='arch'><refentrytitle>pacman</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2013-10-31 08:25:44 +08:00
|
|
|
|
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
|
|
|
|
|
<citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
2011-03-16 03:51:41 +08:00
|
|
|
|
</para>
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
|
|
</refentry>
|
