Description of problem:
It would be extremly handy if it was possible for DNF to install based ks file as in something like dnf install foo.ks and it would read and install based on the ks file.
The usecase for this for administrator to re-use existing ks file in their infrastructure and install directly into OS container which then could be started.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Hello, this is a good idea and we'll keep it in the backlog.
Closely related bug (perhaps to generate the ks): bug 884615.
For OS containers the %post sections probably be needed to be wrapped into something like ( if doable/supportable )
# chroot /containers/container01.example.com/ su - root -c ". ~/.bash_profile; <%post command>"
that's up to the containers. DNF will only use the %packages section I think.
We also need to make this accessible from the API so Anaconda might consider switching to it later.
This will have to be a plugin as it's going to depend on kickstart and we don't want that dep in the core.
Radek, please take care of this one (building a plugin that does just that). Ask the #anaconda guys about how to use python-kickstart to parse out what is needed.
Then in DNF just register a new 'dnf kickstart' Command.
Here's an example of how to register a new command from a plugin:
Documentation is coming. The plugin should use the existing API where at all possible.
The plugin have been implemented. Now it is waiting for the package to be released.
Fantastic great work thanks
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.