11.2. Sharing the installation files on an HTTP or HTTPS server
You can store Kickstart files on an HTTP or HTTPS server to enable automated installations across multiple systems. It eliminates the need for physical media and provides centralized management of installation configurations for efficient system deployment.
Prerequisites
- You have administrator-level access to a server with Red Hat Enterprise Linux 10 on the local network.
- The system to be installed can connect to the server.
Procedure
To store the Kickstart file on an HTTP, install the
httpdpackage:# dnf install httpdOptional: To store the Kickstart file on an HTTPS, install
httpdandmod_sslpackages:# dnf install httpd mod_ssl重要If you use an HTTPS server with a self-signed certificate, you must boot the installation program with the
inst.noverifyssloption.-
Copy the Kickstart file to the HTTP(S) server into a subdirectory of the
/var/www/html/directory. Enable the http service in firewalld.
# firewall-cmd --permanent --add-service=http # firewall-cmd --reloadOptional: Enable the
httpsservice in firewalld:# firewall-cmd --permanent --add-service=https # firewall-cmd --reloadStart the
httpdservice:# systemctl enable --now httpd.serviceThe Kickstart file is now accessible and ready to be used for installation.
When specifying the location of the Kickstart file, use
http://orhttps://as the protocol, the server’s host name or IP address, and the path of the Kickstart file, relative to the HTTP server root. For example, if you are using HTTP, the server’s host name ismyserver.example.com, and you have copied the Kickstart file as/var/www/html/rhel10-install/my-ks.cfg, specifyhttp://myserver.example.com/rhel10-install/my-ks.cfgas the file location.