Verschillen

Dit geeft de verschillen weer tussen de geselecteerde revisie en de huidige revisie van de pagina.

--- installatie_handleidingen:fedora-coreos [2025/09/02 14:53]
abel [add the ignite file]
+++ installatie_handleidingen:fedora-coreos [2025/09/03 21:13] (huidige)
abel [convert the butqane file to an ignite file]
@@ Regel 1: / Regel 1: @@
 ====== Install Fedora Core OS (FCOS) ======
+CoreOS uses an ignite file to determine the parameters for the installation. This can be a file on a disk or a file on a webserver.
+Installation methods for openshift and OKD use this to push installation configurations over ssh.
 ===== create the ignite file =====
 you do this by creating a butane config yaml and converting it to an ignite json using butane.
@@ Regel 8: / Regel 11: @@
 ==== create the butane config file ====
-Create a yaml file with your config, mid the indentation. In this example only a group and a user with a specific uid is created (an exhaustive list of the options for butane config can be found [[https://www.flatcar.org/docs/latest/provisioning/config-transpiler/configuration/|here]]) i name this file //version1.bu//
+Create a yaml file with your config, mid the indentation. In this example only a group and a user with a specific uid is created. I name this file //version1.bu// (an exhaustive list of the options for butane config can be found [[https://www.flatcar.org/docs/latest/provisioning/config-transpiler/configuration/|here]]). A hashed password can be created using:\\
+''mkpasswd --method=yescrypt''\\
+it will ask for your password and returned a hashed password.
 <code yml>
@@ Regel 18: / Regel 23: @@
   users:
     - name: abel
+      password_hash: $y$j9T$z8................
       uid: 700
       primary_group: users
@@ Regel 27: / Regel 33: @@
 ==== convert the butqane file to an ignite file ====
-Then with butane transform it ti the ignite json:
+Then with butane transform it ti the ignite json:\\
-''butane --pretty --strict version1.bu > version1.ign''
+''%%butane --pretty --strict version1.bu > version1.ign%%''
 the resulting json file //version1.ign// looks like:
@@ Regel 49: / Regel 55: @@
         ],
         "name": "abel",
+        "passwordHash": "$y$j9T$z8................",
         "primaryGroup": "users",
         "sshAuthorizedKeys": [
@@ Regel 60: / Regel 67: @@
 </code>
+==== save the ignite file ====
+Copy the previously made ignite file to a separate USB disk formatted with xfs filesystem for use in installation later.
 ===== create an USB installation disk =====
@@ Regel 68: / Regel 78: @@
 and create a bootable installation medium USB stick using ''dd'' or //Rufus//
-==== add the ignite file ====
-copy the previously made ignite file to the USB disk you just made.
 ===== boot and install the target baremetal server =====
 stick the USB install disk in the server, turn on and in the BIOS or in the bootmenu choose the USB device as boot device.
-once the system is booted on the promt enter:
+once the system is booted, insert the seperate stick with the ignite file in the server and mount it.
+On the promt enter:
 ''lsblk''
@@ Regel 82: / Regel 90: @@
 Then start the installation :
-''sudo coreos-installer install /dev/sda --ignition-file version1.ign''
+''%%sudo coreos-installer install /dev/sda --ignition-file /path/to/seperate-USB-stick/version1.ign%%''

Gebruikershulpmiddelen

Site-hulpmiddelen

Verschillen

Paginahulpmiddelen