Kickstart option to prevent creating anaconda-ks.cfg

Solution Verified - Updated -


  • Deployed systems write out a kickstart file to /root/anaconda-ks.cfg that can be used to kickstart similarly configured systems. This is a handy way to generate a kickstart file if you need one. However, in many cases you don't, especially if you already used one to deploy the system in the first place.
  • In these scenarios it is best to remove the file since it contains potentially sensitive information, such as root's password or hash.
  • Previously it could be removed during %post (as noted here:, however in RHEL 7 it is created after %post making it more difficult to cleanup.
  • I would like a kickstart option that would be able to disable the creation of this second kickstart file. This could be used to override the default of creating /root/anaconda-ks.cfg and later cleanup would not be needed.


  • Red Hat Enterprise Linux 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In