On Fri, Feb 28, 2020 at 3:10 PM Ananthu R V <anant...@thoughtworks.com> wrote:
> HI Sinny, > > Thanks for helping us with the logs. We were able to go forward and build > iso with Lorax. We need some more advice on adding additional packages. > What was tried was a custom repo was added to the kickstart > file(interactive-defaults.ks) and specified the packages. But to no luck > the custom packages were not in the final iso. > Silverblue main content comes from custom ostree repo that you would have created. For additional package add those package list in the config and then build the ostree repo. Installed system should have those packages when iso gets installed as it will pull in content for host from the custom ostree repo. So question > 1, Does the kickstart file need to run rpm-ostree in the KS file? > I don't think so 2, Lorax when run shows checking dependencies and comes up with a list of > 773 pkgs. Any idea where this list is? > Part of lorax https://github.com/weldr/lorax/blob/master/share/templates.d/99-generic/runtime-install.tmpl > Regards > *Ananthu* Ramachandran Vineetha | *അനന്തു* രാമചന്ദ്രൻ വിനീത > ThoughtWorks® > > > On Wed, Feb 19, 2020 at 12:38 PM Sinny Kumari <ksi...@gmail.com> wrote: > >> On Wed, Feb 19, 2020 at 9:21 AM Ananthu R V <anant...@thoughtworks.com> >> wrote: >> > >> > Hi Dusty, >> > >> > Would be great if we can find the current build scripts for silverblue. >> I found the one related atomic host and trying to work my way around it. >> And if we can help in anyway to help improve silverblue more than happy to. >> >> I agree with what Dusty recommended, it would be easier to use >> Silverblue ISO and using a custom kickstart that point the install at >> your custom OSTree repo/ref >> >> If you still want to create your own ISO, few pointers which may help >> you to understand how we build Fedora Silverblue ISO today: >> - We use lorax command to build ISO >> - Command which was used to build F31 Silverblue ISO is in log >> >> https://kojipkgs.fedoraproject.org/compose/31/Fedora-31-20191023.0/logs/x86_64/Silverblue/ostree_installer-3/runroot.log >> . On the top of the log you will see a big lorax command passing >> various options. Lot of them are repos link which points to packages >> source location. Interesting line to pick from the log is the one >> which starts from " + lorax --product=Fedora --version=31 >> --release=1.9 " >> - Various configs options which was used is available at >> https://pagure.io/pungi-fedora/blob/f31/f/fedora-final.conf#_747 . It >> contains links to different repos used as well >> >> Hope this helps. >> >> > Regards >> > Ananthu Ramachandran Vineetha | അനന്തു രാമചന്ദ്രൻ വിനീത >> > ThoughtWorks® >> > >> > >> > On Tue, Feb 18, 2020 at 8:22 PM Dusty Mabe <du...@dustymabe.com> wrote: >> >> >> >> >> >> >> >> On 2/18/20 9:39 AM, Ananthu R V wrote: >> >> > Hi Dusty, >> >> > >> >> > Thanks for the update. We were looking at more of a remix which can >> passed on and used by a wider set of people. >> >> > >> >> > Do you think Kickstart approach will work this? My understanding is >> that for this to work the iso has to be modified to point to the custom >> Kickstart. Please correct me if i am wrong. >> >> >> >> It could work to use a custom kickstart, but it's not ideal. Obviously >> it's better to >> >> give them an ISO with all the content baked in. >> >> >> >> > >> >> > I am trying to refer your blog get this working. Would be helpful to >> get detailed look into the current way of how silverblue builds are made. >> >> >> >> Yeah, good luck. It's not rocket science, but it is involved. We'd >> like for it to be >> >> better. >> >> >> >> Dusty >> >> >> >> -- >> http://sinny.io/ >> >
