Correct way to use custom image - rebase or install via ISO - UBlue "after boot" customizations?
Hi,
I built my customized image of Aurora-DX using blue build template. Now wondering, what is the correct / best approach to use this image and/or how to build it?
The point is, that I can install standard Aurora-DX, boot it and rebase to my image. This way I got all aurora flatpaks for example as well as my custom ones from my blue build (from my recipe).
But when I install and boot directly my image ISO, I am missing default Aurora-DX stuff (e.g. their default flatpaks for example) - only my custom ones are installed.
So the question again is, how should I proceed and does this affect only default Aurora flatpaks or I lose this way more standard Aurora-DX "after boot" customizations? (when I am using directly my image without rebase)?
Should I include default aurora flatpaks directly into my recipe as well? That would mitigate the flatpaks issue. But is there more customizations from default Aurora-DX/any Universal Blue image I may be losing? Or is "safer" approach to install default Aurora-DX and rebase to my image (so I get all "after boot" stuff from standard Aurora)?
Thanks a lot!
Solution:Jump to solution
This is actually a missing feature for the generate ISO subcommand. We do have plans to enable this, but the fact of the matter is that the upstream ISO builder needs a list of all the flatpaks that you want to install. The way we're going to go about it is any entry of the default flatpak module will pass in the data to the ISO builder so that it sets up installing flatpaks on install.
6 Replies
Solution
This is actually a missing feature for the generate ISO subcommand. We do have plans to enable this, but the fact of the matter is that the upstream ISO builder needs a list of all the flatpaks that you want to install. The way we're going to go about it is any entry of the default flatpak module will pass in the data to the ISO builder so that it sets up installing flatpaks on install.
So any flat packs that are set up to be installed from the upstream ISO will not end up being in your own personal built ISO
So for now you would suggest the rebase route or to copy flatpaks into my custom recipe from ublue repo? Also do you know if flatpaks is only stuff affected or they are doing more custom stuff there?
I think flat packs are the only thing that is nebulous, mostly because it requires an actual running operating system to get those installed. They can't be in the image as of this moment.
The way our module works is we use a SystemD unit to go and read a list of your flat packs and then install them.
Yeah, I noticed the Blue Build way. So the safer route seems to be include all flatpaks into my recipe...if they are already there, no problem, if not, they will be installed. Thanks a lot.
Not a problem.