You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Louis Abel 0a16a1b5cf
fix grub2-pc package name and comment out sed
3 months ago
live/9 restorecon / likely not needed 3 months ago
README.md fix readme 5 months ago
Rocky-9-Azure.ks clean up azure kickstart 3 months ago
Rocky-9-Container-Base.ks These don't actually work, despite giving a warning to use them in anaconda 5 months ago
Rocky-9-Container-Minimal.ks These don't actually work, despite giving a warning to use them in anaconda 5 months ago
Rocky-9-EC2.ks clean up EC2 kickstart 3 months ago
Rocky-9-GenericCloud.ks fix grub2-pc package name and comment out sed 3 months ago
Rocky-9-KDE.ks remove unsigned him and fix grubby 5 months ago
Rocky-9-MATE.ks restorecon / likely not needed 3 months ago
Rocky-9-Vagrant-Libvirt.ks grow genclo disk, reqpart on vagrant 5 months ago
Rocky-9-Vagrant-VMware.ks Add VMware Vagrant kickstart 5 months ago
Rocky-9-Vagrant-Vbox.ks grow genclo disk, reqpart on vagrant 5 months ago
Rocky-9-Workstation-Lite.ks fix workstation lite welcome tour 5 months ago
Rocky-9-Workstation-Mainline.ks fix dialog 5 months ago
Rocky-9-Workstation.ks remove unsigned him and fix grubby 5 months ago
Rocky-9-XFCE.ks fix XFCE still 5 months ago

README.md

R9 specific kickstarts

This branch has Rocky Linux 9 specific kickstarts. These kickstarts vary between cloud images and live images provided in our repositories and mirrors.

Structure

In the root of the repository are the general kickstarts in use that any user can pick up, use, or modify to their liking to make their own Rocky Linux live images. For those who are curious, in the live directory are the split parts that make the live kickstarts what they are, which you can use ksflatten on if you so choose.

For SIG/Core's usage, we use the live area as a "working" directory, where we use the split parts in our automation for the images and the pre-flattened versions are there for the convenience of all users.

Building Live Images

To build live images, you will need to use livecd-creator or livemedia-creator. The former is simpler to use and generally works without many issues. The latter can be a bit more tricky to work with and typically runs the installer virtually. However, it can be used without a virtual machine like in a mock shell.

Optionally, it is possible to use empanadas found in the SIG/Core toolkit.

Automatic: Using empanadas

To be filled.

Manual: Using livemedia-creator

To use livemedia-creator without using virt, you can use a mock shell. To setup a mock chroot for the purpose of building a live image, you would set it up like so:

# Install mock if you haven't already
% dnf install epel-release -y
% dnf install mock -y

# Add a user to the mock group
% usermod -a -G mock user

# As the user, setup the mock environment
% mock -r rocky-9-x86_64 --init
% mock -r rocky-9-x86_64 --install lorax-lmc-novirt vim-minimal pykickstart git
# You may need to be in permissive mode temporarily if you have issues
% setenforce 0
# Enter the shell
% mock -r rocky-9-x86_64 --shell --isolation=simple --enable-network

# Clone the kickstarts and run an installation
% git clone https://github.com/rocky-linux/kickstarts
% cd kickstarts
% livemedia-creator --ks Rocky-9-Workstation.ks \
  --no-virt \
  --resultdir /var/lmc \
  --project="Rocky Linux" \
  --make-iso \
  --volid Rocky-Workstation-9 \
  --iso-only \
  --iso-name Rocky-Workstation-9-x86_64.iso \
  --releasever=9 \
  --nomacboot  # This option is important to set, mkfs.hfsplus is not available

With the example above, all of the results will appear in /var/lib/mock/rocky-9-x86_64/root/var/lmc.