systemd-nspawn (Русский) - ArchWiki

# systemd-nspawn (Русский)

From ArchWiki

Related articles

- systemd
- Linux Containers
- systemd-networkd
- Docker
- Lxc-systemd

systemd-nspawn аналогична команде chroot, но это chroot на стероидах.

systemd-nspawn но он может быть использован для выполнения команды или OS в контейнере окружения. Он является более мощным, чем chroot так как он полностью виртуализирует иерархии файловой системы, а также дерево процессов, различные подсистемы IPC и имени хоста и домена.

systemd-nspawn ограничивает доступ к различным интерфейсам ядра в контейнере только для чтения, например, `/sys`, `/proc/sys` or `/sys/fs/selinux`. Сетевые интерфейсы и системные часы не могут быть изменены внутри контейнера. Узлы устройства не могут быть созданы. Хост-система не может быть перезагружен и модули ядра не могут быть загружены из внутри контейнера.

Этот механизм отличается от Lxc-systemd или Libvirt-lxc, так как это более простой инструмент для настройки

## Установка

systemd-nspawn является частью и упаковываются с systemd.

## Примеры

### Создание и загрузка минимального дистрибутива Arch Linux в контейнере

Tip: You can use mkosi to do this for arch and other distributions fully automatically and with easy further customization.

С начала установим пакет arch-install-scripts.

Далее создадим папку для хранения контейнера, в примере используется `~/MyContainer`.

Далее, мы используем pacstrap для установки базового экземпляра системы в контейнере. Как минимум нам нужно установить base группу

1. pacstrap -i -c -d ~/MyContainer base [additional pkgs/groups]

Tip: `-i` Опция автовыбора пакетов. AТак как вам не нужно установить ядро Linux в контейнере, вы можете удалить его из списка выбора пакета для экономии места. Подробнее Pacman#Usage.
Note: Пакет linux-firmware требуемый linux, который входит в base группу и не требуется для запуска контейнера, вызывает некоторые проблемы с `systemd-tmpfiles-setup.service` во время процесса загрузки с `systemd-nspawn`. Можно установить base группу, но исключая пакет linux и его зависимости при сборке контейнера с помощью `# pacstrap -i -c -d ~/MyContainer base --ignore linux [additional pkgs/groups]`. Флаг `--ignore` будет просто передан pacman. См. FS#46591 для получения дополнительной информации.

После того, как ваша установка будет завершена, загружается в контейнер:

1. systemd-nspawn -b -D ~/MyContainer

эта `-b` -b опция загрузки контейнера (т.е. запустить `systemd`, как PID = 1), вместо того, чтобы просто запустить оболочку. `-D` указывает каталог, который становится корневым каталогом контейнера и `-n` создаст частную сеть между хостом и контейнером.

После запуска контейнера, войдите в систему как "root" без пароля.

Контейнер может быть выключен, запустив `poweroff` внутри контейнера. От root, контейнеры можно управлять с помощью метода machinectlинструмент.

Note: Чтобы завершить сеанс из контейнера, удерживайте клавишу `Ctrl` и быстро нажмите `]` три раза. Non-US keyboard users should use `%` instead of `]`.

#### Bootstrap Arch Linux i686 inside x86_64 host

Можно установить минимальный I686 Arch Linux внутри подкаталога и использовать его в качестве контейнера systemd-nspawn вместо chroot или virtualization. Это полезно для тестирования компиляции `PKGBUILD` для i686 и других задач. Убедитесь, что используете `pacman.сonf` без `multilib` репозитория.

     # pacman_conf=/tmp/pacman.conf # this is pacman.conf without multilib
     # mkdir /mnt/i686-archlinux
     # linux32 pacstrap -C "$pacman_conf" -di /mnt/i686-archlinux base base-devel

Вы можете исключить `linux` из `base` группы, поскольку результирующий загрузочный каталог не предназначен для загрузки на реальном или виртуальном оборудовании.

Чтобы запустить полученный экземпляр i686 Arch Linux systemd-nspawn, выполните следующую команду.

     # linux32 systemd-nspawn -D /mnt/i686-archlinux

### Create a Debian or Ubuntu environment

Install debootstrap, gnupg1AUR, and one or both of debian-archive-keyring and ubuntu-keyring (obviously install the keyrings for the distros you want).

Note: systemd-nspawn requires that the operating system in the container has systemd running as PID 1 and systemd-nspawn is installed in the container. This means Ubuntu before 15.04 will not work out of the box and requires additional configuration to switch from upstart to systemd. Also make sure that the `systemd-container` package is installed on the container system.

From there it's rather easy to setup Debian or Ubuntu environments:

    # cd /var/lib/machines
    # debootstrap <codename> myContainer <repository-url>

For Debian valid code names are either the rolling names like "stable" and "testing" or release names like "stretch" and "sid", for Ubuntu the code name like "xenial" or "zesty" should be used. A complete list of codenames is in `/usr/share/debootstrap/scripts`. In case of a Debian image the "repository-url" can be `http://deb.debian.org/debian/`. For an Ubuntu image, the "repository-url" can be `http://archive.ubuntu.com/ubuntu/`.

Unlike Arch, Debian and Ubuntu will not let you login without a password on first login. To set the root password login without the '-b' option and set a password:

    # systemd-nspawn -D myContainer
    # passwd
    # logout

If the above didn't work. One can start the container and use these commands instead:

    # systemd-nspawn -b -D myContainer  #Starts the container
    # machinectl shell root@myContainer /bin/bash  #Get a root bash shell
    # passwd
    # logout

### Creating private users (unprivileged containers)

systemd-nspawn supports unprivileged containers, though the containers need to be booted as root.

Note: This feature requires user_namespaces(7), which are disabled in the official Arch kernels due to security reasons presented in FS#36969. Unofficial packages linux-usernsAUR[ссылка недействительна: package not found] and linux-lts-usernsAUR[ссылка недействительна: package not found] are available.

The easiest way to do this is to let systemd-nspawn decide everything:

    # systemd-nspawn -UD myContainer
    # passwd
    # logout
    # systemd-nspawn -bUD myContainer

Here systemd-nspawn will see if the owner of the directory is being used, if not it will use that as base and 65536 IDs above it. On the other hand if the UID/GID is in use it will randomly pick an unused range of 65536 IDs from 524288 - 1878982656 and use them.

Note:

- The base of the range chosen is always a multiple of 65536.
- `-U` and `--private-users=pick` is the same, if kernel supports user namespaces. `--private-users=pick` also implies `--private-users-chown`, see systemd-nspawn(1) for details.

You can also specify the UID/GID of the container manually:

    # systemd-nspawn -D myContainer --private-users=1354956800:65536 --private-users-chown
    # passwd
    # logout
    # systemd-nspawn -bUD myContainer

While booting the container you could still use `--private-users=1354956800:65536` with `--private-users-chown`, but it is unnecessarily complicated, let `-U` handle it after the assigning the IDs.

### Enable container on boot

When using a container frequently, you may want to start it on boot.

First enable the `machines.target` target, then `systemd-nspawn@myContainer.service`, where `myContainer` is an nspawn container in `/var/lib/machines`.

Tip: To customize the startup of a container, edit the `systemd-nspawn@myContainer` unit instance. See systemd-nspawn(1) for all options.

### Build and test packages

See Creating packages for other distributions for example uses.

## Management

### machinectl

Note: The machinectl tool requires systemd and dbus to be installed in the container. See [1] for detailed discussion.

Managing your containers is essentially done with the `machinectl` command. See machinectl(1) for details.

Examples:

Spawn a new shell inside a running container:

    $ machinectl login MyContainer

Show detailed information about a container:

    $ machinectl status MyContainer

Reboot a container:

    $ machinectl reboot MyContainer

Poweroff a container:

    $ machinectl poweroff MyContainer

Tip: Poweroff and reboot operations can be performed from within a container session using the systemctl `poweroff` or `reboot` commands.

Download an image:

    # machinectl pull-tar URL name

### systemd toolchain

Much of the core systemd toolchain has been updated to work with containers. Tools that do usually provide a `-M, --machine=` option which will take a container name as argument.

Examples:

See journal logs for a particular machine:

    $ journalctl -M MyContainer

Show control group contents:

    $ systemd-cgls -M MyContainer

See startup time of container:

    $ systemd-analyze -M MyContainer

For an overview of resource usage:

    $ systemd-cgtop

## Tips and tricks

### Use an X environment

See Xhost and Change root#Run graphical applications from chroot.

You will need to set the `DISPLAY` environment variable inside your container session to connect to the external X server.

X stores some required files in the `/tmp` directory. In order for your container to display anything, it needs access to those files. To do so, append the `--bind=/tmp/.X11-unix:/tmp/.X11-unix` option when starting the container.

### Run Firefox

See Firefox tweaks.

### Access host filesystem

See `--bind` and `--bind-ro` in systemd-nspawn(1).

If both the host and the container are Arch Linux, then one could, for example, share the pacman cache:

    # systemd-nspawn --bind=/var/cache/pacman/pkg

Or you can specify per-container bind using the file:

    /etc/systemd/nspawn/my-container.nspawn

    [Files]
    Bind=/var/cache/pacman/pkg

See #Specify per-container settings.

### Configure networking

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Systemd-nspawn (Русский)#)

For the most simple setup, allowing outgoing connections to the internet, you can use systemd-networkd for network management and DHCP and `systemd-resolved` for DNS.

    # systemctl enable --now systemd-networkd systemd-resolved
    # ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf # let systemd-resolved manage /etc/resolv.conf

This assumes you have started `systemd-nspawn` with the `-n` switch, creating a virtual Ethernet link to the host.

Instead of using `systemd-resolved` you can also manually edit your container's `/etc/resolv.conf` by adding your DNS server's IP address.

Note the canonical systemd-networkd host and container .network files are from https://github.com/systemd/systemd/tree/master/network .

See systemd-networkd#Usage with containers for more complex examples.

#### nsswitch.conf

This article or section is a candidate for merging with systemd-networkd.

Notes: please use the second argument of the template to provide more detailed indications. (Discuss in Talk:Systemd-nspawn (Русский)#)

To make it easier to connect to a container from the host, you can enable local DNS resolution for container names. In `/etc/nsswitch.conf`, add `mymachines` to the `hosts:` section, e.g.

    hosts: files mymachines dns myhostname

Then, any DNS lookup for hostname `foo` on the host will first consult `/etc/hosts`, then the names of local containers, then upstream DNS etc.

#### Use host networking

To disable private networking used by containers started with `machinectl start MyContainer` edit the configuration of `systemd-nspawn@.service` with

    # systemctl edit systemd-nspawn@.service

and set the `ExecStart=` option without the `--network-veth` parameter unlike the original service:

    /etc/systemd/system/systemd-nspawn@.service.d/override.conf

    [Service]
    ExecStart=
    ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --machine=%I

The newly started containers will use the hosts networking.

#### Virtual Ethernet interfaces

If a container is started with `systemd-nspawn ... -n`, systemd will automatically create one virtual Ethernet interface on the host, and one in the container, connected by a virtual Ethernet cable.

If the name of the container is `foo`, the name of the virtual Ethernet interface on the host is `ve-foo`. The name of the virtual Ethernet interface in the container is always `host0`.

When examining the interfaces with `ip link`, interface names will be shown with a suffix, such as `ve-foo@if2` and `host0@if9`. The `@ifN` is not actually part of the name of the interface; instead, `ip link` appends this information to indicate which "slot" the virtual Ethernet cable connects to on the other end.

For example, a host virtual Ethernet interface shown as `ve-foo@if2` will connect to container `foo`, and inside the container to the second network interface -- the one shown with index 2 when running `ip link` inside the container. Similarly, in the container, the interface named `host0@if9` will connect to the 9th slot on the host.

### Run on a non-systemd system

See Init#systemd-nspawn.

### Specify per-container settings

To specify per-container settings and not overrides for all (e.g. bind a directory to only one container), the .nspawn files can be used. See systemd.nspawn(5) for details.

### Use Btrfs subvolume as container root

To use a Btrfs subvolume as a template for the container's root, use the `--template` flag. This takes a snapshot of the subvolume and populates the root directory for the container with it.

Note: If the template path specified is not the root of a subvolume, the entire tree is copied. This will be very time consuming.

For example, to use a snapshot located at `/.snapshots/403/snapshot`:

    # systemd-nspawn --template=/.snapshots/403/snapshots -b -D my-container

where `my-container` is the name of the directory that will be created for the container. After powering off, the newly created subvolume is retained.

### Use temporary Btrfs snapshot of container

One can use the `--ephemeral` or `-x` flag to create a temporary btrfs snapshot of the container and use it as the container root. Any changes made while booted in the container will be lost. For example:

    # systemd-nspawn -D my-container -xb

where my-container is the directory of an existing container or system. For example, if `/` is a btrfs subvolume one could create an ephemeral container of the currently running host system by doing:

    # systemd-nspawn -D / -xb

After powering off the container, the btrfs subvolume that was created is immediately removed.

## Troubleshooting

### root login fails

If you get the following error when you try to login (i.e. using `machinectl login <name>`):

    arch-nspawn login: root
    Login incorrect

And `journalctl` shows:

    pam_securetty(login:auth): access denied: tty 'pts/0' is not secure !

Add `pts/0` to the list of terminal names in `/etc/securetty` on the container filesystem, see [2]. You can also opt to delete `/etc/securetty` on the container to allow root to login to any tty, see [3].

### Unable to upgrade some packages on the container

It can sometimes be impossible to upgrade some packages on the container, filesystem being a perfect example. The issue is due to `/sys` being mounted as Read Only. The workaround is to remount the directory in Read Write when running `mount -o remount,rw -t sysfs sysfs /sys`, do the upgrade then reboot the container.

## See also

- Automatic console login
- machinectl man page
- systemd-nspawn man page
- Creating containers with systemd-nspawn
- Presentation by Lennart Pottering on systemd-nspawn
- Running Firefox in a systemd-nspawn container

Category:

- Virtualization (Русский)

Hidden categories:

- Pages with broken package links
- Pages or sections flagged with Template:Style
- Pages or sections flagged with Template:Merge