summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordavid2020-06-18 11:23:29 +0000
committeradmin2020-06-18 11:23:29 +0000
commit5e20033605001ea6e3d8e7250cae3e9be34fffbe (patch)
tree6d35fc0f9eabc5158228bac1199ebab347b258cf
parent2cc1ec1f2b9af57742c2da7e3656b947be3d3ead (diff)
-rw-r--r--doc/forum/recommendations_for_setting_up__a_Fedora_chroot_on_a_Debian_host.mdwn9
1 files changed, 9 insertions, 0 deletions
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.