Automate or script a Fedora Silverblue install : with kickstart files or other ways

Project Discussion
#1

I would like to automate the installation of Fedora SIlverblue. For now I have to do all those steps:

  • Get the Silverblue image: Team Silverblue — Download
  • install the Silverblue image on a USB installation disk
  • Boot the USB installation disk
  • Configure with GUI Anaconda the desired Fedora Silverblue installation settings
  • MOST IMPORTANTLY: setup partitioning to separate /home from other system partitions (/boot and the ostree partition)
  • Install and reboot Fedora Silverblue
  • Do post -install work in GUI (user accounts, connectivity, timezone, etc…)
  • Do post installation of programs from flatpak (via flathub or Gnome Software)
  • Do several installation and reboot for programs that aren’t distributed with flatpak but need install from rpm (via rpm-ostree and layering)

Is it possible to do any or all those steps in an automated or scripted way to install Fedora Silverblue ? So that I can duplicate and deploy those settings to several computers ?

Are there some ready to use kickstart files that may be customized , and how to use them for a Fedora Silverblue install ?

1 Like
#2

Hello @mahdiaqallal ,
Welcome to the :fedora: discussion area. I think there are kickstart examples for Workstation but I haven’t seen one for Silverblue, not to say someone hasn’t done that. One way you could go is to try Fedora Core OS since it uses ignition files to do everything from partitioning to installing SW to setting up the user. You could think of it as Silverblue Server. If there was such a thing.

1 Like
#3

Thanks @jakfrost for your reply.
Could you please expand your answer because I didn’t finde any documentation stating ignition files could be used in Silverblue…

Dear Silverblue community I really need you contribution on this topic.

#4

Hello @mahdiaqallal,
I’m referring to the fact Fedora CoreOS and Silverblue are both Fedora Linux in an Atomic OS using a hybrid packaging system. While Silverblue uses Anaconda for it’s installer, Fedora CoreOS uses an ignition file but also has a Live USB offering now too I think. Anyway, the ignotion file is created from a Yaml file you make that describes your installation, disk partitioning and all down to the installed software and user setup. It is largely more for an administered ecosystem but can be used on bare metal single user setup’s too. You can find the doc’s at https://docs.fedoraproject.org/en-US/fedora-coreos/ where you can learn more about it.

#5

Let’s be careful here and not mix two things. Ignition is only used in Fedora CoreOS for now and Fedora CoreOS is for server/cluster/cloud deployments.

For Fedora Silverblue/Kinoite, you currently only have Kickstart as an option for install time configuration and then Ansible, Fleet Commander (requires FreeIPA or Active Directory) or other management tools once you have a system running.

For Kickstart, see:

Note however that some option/commands may not work as Silverblue/Kinoite is installed a bit differently.

#6

You can get an example Kickstart by manually performing an installation via Anaconda and then looking in the /root folder for anaconda-ks.cfg:

#7

I understand that, but ignition can be used to make a single user system if desired. It is also in some ways a more flexible approach to setting up a system initially. Anyway, I like the kickstart approach too.

#8

I’m not sure I follow here. Kickstarts can not be used on Fedora CoreOS and Ignition can not be used on Fedora Silverblue/Kinoite. This may change in the future but this is the state right now.

The initial question was about Fedora Silverblue thus why I highlighted that here.

#9

Sorry I replied now actually.

#10

Thank you all for your replies !

I’m customizing my future kickstart file as proposed by @siosm , using /root/anaconda-ks.cfg from a previous install as a template.

My first goal is to have formatted in btrfs the /home folder in a separate partition than /root etc…

  1. Since in the rpm-ostree system the tree is read-only except /var and /etc (in my understanding) how do I configure the syntax for the #Disk partitioning information part in the ks file

btrfs /home --subvol --name=home LABEL=home_fedora
or
btrfs /var/home --subvol --name=home LABEL=home_fedora

  1. To have applications installed beyond those included in Silverblue, what command lines to insert and where should I include them so as to install :
  • include new repositories (rpmfusion, copr etc…)
  • Flatpak commands installations
  • rpm installations when necessary

I’m quite new to Silverblue, so thanks for your help !

#11

No worries and thanks for all you do around here. I wanted to make sure there was no confusion.

#12

For 1 I think it’s the second option /var/home but I’m not really familiar with btrfs enough.
For 2. It might be easier to do that post installation via a script or via Ansible. There are example commands in the docs to install Flatpaks, etc.

#13

When I did it, I made my subvolumes like so …
btrfs subvolume mounted at /, btrfs subvolume mounted at /var and btrfs subvolume mounted at /home. I am uncertain how the symlinking would go in the kickstart file way, but with anaconda, and using advanced blivet gui in the installer, I get the correct symlink setup (so home is /var/home in use).

1 Like