lorax/share/composer/ext4-filesystem.ks

# Lorax Composer filesystem output kickstart template

# Firewall configuration
firewall --enabled

# NOTE: The root account is locked by default
# Network information
network  --bootproto=dhcp --onboot=on --activate
# System keyboard
keyboard --xlayouts=us --vckeymap=us
# System language
lang en_US.UTF-8
# SELinux configuration
selinux --enforcing
# Installation logging level
logging --level=info
# Shutdown after installation
shutdown
# System timezone
timezone  US/Eastern
# System bootloader configuration (unpartitioned fs image doesn't use a bootloader)
bootloader --location=none

%post
# Remove random-seed
rm /var/lib/systemd/random-seed

# Clear /etc/machine-id
rm /etc/machine-id
touch /etc/machine-id
%end

%packages --nobase
# Packages requires to support this output format go here
selinux-policy-targeted
# Enable networking by removing the config file that disables it
-NetworkManager-config-server

# NOTE lorax-composer will add the blueprint packages below here, including the final %end
Add support for building ext4 filesystem images. 2018-03-22 19:25:27 +00:00			`# Lorax Composer filesystem output kickstart template`

			`# Firewall configuration`
			`firewall --enabled`

Lock the root account, except on live-iso If we leave the root account w/o a password people will use it that way, leading to insecure images. Also if we use a default password. So lock the root account in the templates. Users will need to do one of these things: 1. Use [[customizations.user]] in their blueprint to configure root or another user. 2. Use [[customizations.sshkey]] to set a key for root 2. Install a package that configures a user at install time 3. Install a package that sets up a user at boot time (eg. cloud-init) This also drops the auth line from the kickstart templates, allowing it to use the default password algoritm instead of md5. Resolves: rhbz#1626120 2018-08-08 22:46:16 +00:00			`# NOTE: The root account is locked by default`
Add support for building ext4 filesystem images. 2018-03-22 19:25:27 +00:00			`# Network information`
			`network --bootproto=dhcp --onboot=on --activate`
			`# System keyboard`
			`keyboard --xlayouts=us --vckeymap=us`
			`# System language`
			`lang en_US.UTF-8`
			`# SELinux configuration`
			`selinux --enforcing`
			`# Installation logging level`
			`logging --level=info`
			`# Shutdown after installation`
			`shutdown`
			`# System timezone`
			`timezone US/Eastern`
Move disklabel and UEFI support to compose.py Currently we are making MBR disk images for qcow2 and partitioned disk, so the UEFI packages aren't required at this point. Move the clearpart command into compose.py so that in the futute it can use clearpart --disklabel to create a GPT image, and add the required packages to the package set. 2018-08-08 15:44:01 +00:00			`# System bootloader configuration (unpartitioned fs image doesn't use a bootloader)`
Add support for building ext4 filesystem images. 2018-03-22 19:25:27 +00:00			`bootloader --location=none`

			`%post`
			`# Remove random-seed`
			`rm /var/lib/systemd/random-seed`
Replace /etc/machine-id with an empty file Since these images can be used to create multiple machines, they should not have a unique machine-id attached to them. Replace /etc/machine-id with an empty file so that it will be regenerated at boot time. (cherry picked from commit 6fab72d894cd0c59ff798502d5c30f814f1a4948) Related: rhbz#1656105 2018-10-05 18:27:28 +00:00
			`# Clear /etc/machine-id`
			`rm /etc/machine-id`
			`touch /etc/machine-id`
Add support for building ext4 filesystem images. 2018-03-22 19:25:27 +00:00			`%end`

			`%packages --nobase`
lorax-composer: Install selinux-policy-targeted in images This is required to ensure that SELinux is configured properly while building. It fixes the problem with building tar, and should be installed in the other image types for consistency. Resolves: rhbz#1654795 2018-11-27 21:56:00 +00:00			`# Packages requires to support this output format go here`
			`selinux-policy-targeted`
Enable networking in lorax-composer templates Because anaconda --dirinstall is used the kickstart's network like isn't processed at all. So we need to remove the NetworkManager-server-config package which disables networking. Resolves: rhbz#1710877 2019-06-17 18:24:27 +00:00			`# Enable networking by removing the config file that disables it`
			`-NetworkManager-config-server`
Add support for building ext4 filesystem images. 2018-03-22 19:25:27 +00:00
Lock the root account, except on live-iso If we leave the root account w/o a password people will use it that way, leading to insecure images. Also if we use a default password. So lock the root account in the templates. Users will need to do one of these things: 1. Use [[customizations.user]] in their blueprint to configure root or another user. 2. Use [[customizations.sshkey]] to set a key for root 2. Install a package that configures a user at install time 3. Install a package that sets up a user at boot time (eg. cloud-init) This also drops the auth line from the kickstart templates, allowing it to use the default password algoritm instead of md5. Resolves: rhbz#1626120 2018-08-08 22:46:16 +00:00			`# NOTE lorax-composer will add the blueprint packages below here, including the final %end`