Go to file
2024-02-14 16:11:24 -07:00
cloud add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
container add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
live/10 add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
vagrant add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
README.md add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Azure-Base.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Azure-LVM.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Container-Base.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Container-Minimal.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Container-UBI.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-EC2-Base.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-EC2-LVM.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-GenericArm-Minimal.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-GenericCloud-Base.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-GenericCloud-LVM.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-OCP-Base.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-RPI-Base.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Vagrant-Libvirt.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Vagrant-Vbox.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00
Rocky-10-Vagrant-VMware.ks add initial rocky 10 kickstarts 2024-02-14 16:11:24 -07:00

R9 specific kickstarts

This branch has Rocky Linux 10 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, cloud images, and so on. These kickstarts are generated by templates that live in the various directories in this repository.

  • cloud -> Cloud image templates
  • live -> Live image templates
  • container -> Container image templates

These kickstarts are generated using ksflatten. Changes made to the kickstarts generally match between the templates and the full kickstarts in the root.

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. This is easier than using the pre-made ones in empanadas.

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-10-x86_64 --init
% mock -r rocky-10-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-10-x86_64 --shell --isolation=simple --enable-network

# Clone the kickstarts and run an installation
% git clone https://github.com/rocky-linux/kickstarts -b r9
% 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-10-x86_64/root/var/lmc.