Anaconda Kickstart Documentation

Authors:Brian C. Lane <>

Anaconda uses kickstart to automate installation and as a data store for the user interface. It also extends the kickstart commands documented here by adding a new kickstart section named %anaconda where commands to control the behavior of Anaconda will be defined.


program: pwpolicy <name> [--minlen=LENGTH] [--minquality=QUALITY] [--strict|notstrict] [--emptyok|notempty] [--changesok|nochanges]

Set the policy to use for the named password entry.

Name of the password entry, currently supported values are: root, user and luks
--minlen (6)
Minimum password length. This is passed on to libpwquality.
--minquality (1)
Minimum libpwquality to consider good. When using --strict it will not allow passwords with a quality lower than this.
Strict password enforcement. Passwords not meeting the --minquality level will not be allowed.
--notstrict (DEFAULT)
Passwords not meeting the --minquality level will be allowed after Done is clicked twice.
--emptyok (DEFAULT)
Allow empty password.
Don’t allow an empty password
Allow UI to be used to change the password/user when it has already been set in the kickstart.
--nochanges (DEFAULT)
Do not allow UI to be used to change the password/user if it has been set in the kickstart.


installclass --name=<name>

Require the specified install class to be used for the installation. Otherwise, the best available install class will be used.


Name of the required install class.

The defaults for interactive installations are set in the /usr/share/anaconda/interactive-defaults.ks file provided by Anaconda. If a product, such as Fedora Workstation, wishes to override them then a product.img needs to be created with a new version of the file included.

When using a kickstart the defaults can be overridded by placing an %anaconda section into the kickstart, like this:

pwpolicy root --minlen=10 --minquality=60 --strict --notempty --nochanges


The commit message for pwpolicy included some incorrect examples.