Rocky touchless custom iso Creation - Rocky 9.1

Rocky Linux General
1

Created a touchless custom iso file using “mkisofs”. While booting the iso the installation source, and the installation destination is not detecting automatically.
We need to create a touchless installation iso file. kindly advice us.

Please find the kickstart file below.

# Use graphical install
graphical
repo --name="minimal" --baseurl=file:///run/install/sources/mount-0000-cdrom/minimal

%addon com_redhat_kdump --enable --reserve-mb='auto'

%end

# Keyboard layouts
keyboard --xlayouts='us'
# System language
lang en_US.UTF-8

# Use CDROM installation media
cdrom

# Network information
%packages
@^minimal-environment
vim
net-tools
telnet
zip
wget
unzip
device-mapper-persistent-data
lvm2
yum-utils
docker-ce
docker-ce-cli
containerd.io
python3
epel-release
chrony
ntpstat
firewalld
coreutils
createrepo
jq
-iwl1000-firmware
-iwl100-firmware
-iwl105-firmware
-iwl135-firmware
-iwl2000-firmware
-iwl2030-firmware
-iwl3160-firmware
-iwl5000-firmware
-iwl5150-firmware
-iwl6000g2a-firmware
-iwl6050-firmware
-iwl7260-firmware
%end

# Run the Setup Agent on first boot
firstboot --enable

# Generated using Blivet version 3.4.0
ignoredisk --only-use=sda
autopart
# Partition clearing information
clearpart --none --initlabel

#timesource --ntp-server=40.81.94.65
# System timezone
timezone --isUtc Etc/GMT

# Root password
rootpw --iscrypted --allow-ssh <enctipted passwd>

# Reboot after installation
reboot
2

Note: I did apply preformatted text format to your post.

What is a “touchless” iso?

3

he means hands off install.
so a rough guide where to look, as im not writing war and peace on how to do this.

if your kickstart file is not working, do an interactive install to completion, and then the best template you can have to start is dumped in the root directory of the resulting build as anaconda-ks.cfg

then add a %pre and a %post section to the file, containing typical bash commands to install rpm’s update/edit files, etc to achieve your final goal.
the pre is pre the first boot, the post is after the first boot.

a good start is redhats documentation 32.3. Creating the Kickstart File Red Hat Enterprise Linux 6 | Red Hat Customer Portal

this process is still pretty much the same since rhel 6 but will change drastically when fedora moves to a different install method soon.

all downstreams will eventually catch up.
regards peter