From ed936996800c4af3a498ecc513de0a4c3e4db3c9 Mon Sep 17 00:00:00 2001 From: Alexandre GUIOT--VALENTIN Date: Apr 28 2022 19:33:09 +0000 Subject: Fix typo in nspawn-install doc `machinctl` -> `machinectl` --- diff --git a/docs/modules/ROOT/pages/container-nspawn-install.adoc b/docs/modules/ROOT/pages/container-nspawn-install.adoc index 38ca55e..91686f5 100644 --- a/docs/modules/ROOT/pages/container-nspawn-install.adoc +++ b/docs/modules/ROOT/pages/container-nspawn-install.adoc @@ -17,7 +17,7 @@ But of course a container can also be operated with other variations of a networ 1. *Create a container storage area* + -The systemd-nspawn tools like machinctl look for containers in `/var/lib/machines` first. This directory is also created during the installation of the programs if it does not exist. +The systemd-nspawn tools like machinectl look for containers in `/var/lib/machines` first. This directory is also created during the installation of the programs if it does not exist. + Following the Fedora server storage scheme, create a logical volume, create a file system and mount it to `/var/lib/machines`. The tools can use BTRFS properties, so this can be used as a filesystem in this case. If you don't want to follow the Fedora Server rationale, skip this step.