To configure a kickstart file for automated CentOS installation, start with a template, customize essential sections like language, disk setup, and package selection, place the file where the installer can access it, and test it via bootable media or PXE. Begin by copying an existing sample from /root/anaconda-ks.cfg or use a minimal example. Define general settings such as keyboard, language, and timezone. Specify the installation method using url or cdrom. Configure disk layout with clearpart, bootloader, and autopart directives. Set root password, authentication options, and firewall settings. Select packages under %packages, such as @core or GUI components like @base and @x11. Use %post to run custom commands post-installation. Encrypt passwords using openssl passwd if needed. Test the file in a VM before deploying. Append ks=URL at boot or set up PXE for remote installations. This ensures consistent, error-free deployments across environments.

Setting up a kickstart file for automated CentOS installation is one of the most efficient ways to deploy systems consistently and quickly. Whether you're managing a small lab or a large data center, automation through kickstart can save time and reduce errors.

Understanding the Basics of Kickstart

A kickstart file is essentially a script that tells the CentOS installer how to set up your system automatically. It contains answers to all the questions the installer would normally ask during a manual install—like disk partitioning, package selection, user creation, and more.

You don't need to write everything from scratch. The easiest way to start is by using the sample kickstart file generated after installing CentOS manually—it's usually saved at /root/anaconda-ks.cfg.

Here are some essential sections every kickstart file includes:

• General setup: Language, keyboard layout, timezone
• Installation method: Where the installer should pull packages from (CDROM, NFS, HTTP, etc.)
• Disk configuration: Partitioning scheme and bootloader settings
• User authentication: Root password, shadow password usage
• Package selection: Which groups or individual packages to install
• Post-installation commands: Custom scripts to run after installation completes

Writing Your First Kickstart File

Start with a basic template and customize it based on your needs. Here’s a minimal example:

#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
install
url --url="http://mirror.centos.org/centos/7/os/x86_64/"
text
keyboard 'us'
lang en_US.UTF-8

network --bootproto=dhcp --device=eth0 --onboot=on
rootpw --plaintext mypassword
firewall --disabled
authconfig --enableshadow --passalgo=sha512
selinux --disabled
timezone Asia/Shanghai --isUtc
bootloader --location=mbr
clearpart --all --initlabel
autopart

%packages
@core
%end

%post
echo "Hello World" > /root/hello.txt
%end

Some key points when writing your own:

• Use url if you're installing over the network, or cdrom if booting from physical media.
• You can encrypt passwords using --iscrypted and provide an encrypted string via openssl passwd.
• If you want a GUI environment, add @base and @x11 in %packages.
• In %post, you can run any shell commands to configure the system post-install.

Testing and Using the Kickstart File

Once you've written your kickstart file, place it where the installer can access it—this could be a web server, local drive, or even embedded in a custom ISO.

To test it:

1. Create a bootable USB or CD using the CentOS ISO.
2. Edit the boot command line at the boot prompt and append:

   ks=http://yourserver/ks.cfg

3. The installer will fetch the file and begin unattended installation.

If you're doing multiple deployments, consider setting up a PXE boot environment so you can kick off installations remotely without needing physical media.

Also, make sure to test your kickstart file in a virtual machine first—VirtualBox or KVM works well for this. It helps catch syntax issues or misconfigurations before rolling out to real hardware.

---

That’s basically how you configure a kickstart file for automated CentOS installation. It’s not overly complicated, but there are enough details to pay attention to—especially around partitioning and post-install scripting.

The above is the detailed content of How to configure a kickstart file for automated CentOS installation?. For more information, please follow other related articles on the PHP Chinese website!