From 5e20033605001ea6e3d8e7250cae3e9be34fffbe Mon Sep 17 00:00:00 2001 From: david Date: Thu, 18 Jun 2020 11:23:29 +0000 Subject: --- ...dations_for_setting_up__a_Fedora_chroot_on_a_Debian_host.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/recommendations_for_setting_up__a_Fedora_chroot_on_a_Debian_host.mdwn diff --git a/doc/forum/recommendations_for_setting_up__a_Fedora_chroot_on_a_Debian_host.mdwn b/doc/forum/recommendations_for_setting_up__a_Fedora_chroot_on_a_Debian_host.mdwn new file mode 100644 index 00000000..c12a7556 --- /dev/null +++ b/doc/forum/recommendations_for_setting_up__a_Fedora_chroot_on_a_Debian_host.mdwn @@ -0,0 +1,9 @@ +I'd like a way to set up Fedora chroots for testing purposes on my Debian workstations. Currently I use the example from the systemd-nspawn manpage +[[!format text """ +# machinectl pull-raw --verify=no \ + https://download.fedoraproject.org/pub/fedora/linux/releases/31/Cloud/x86_64/images/Fedora-Cloud-Base-31-1.9.x86_64.raw.xz \ + Fedora-Cloud-Base-31-1.9.x86-64 +# systemd-nspawn -M Fedora-Cloud-Base-31-1.9.x86-64 +"""]] + +If I understand correctly the existing Systemd.container function needs a way to make a chroot. -- cgit v1.2.3