not sure if this correct place or talked already, but would it be nice to make Atomic installer where you can click and choose what apps/softwares you want to enable as base and then it gathers and builds it like if you are using nvidia clicking add nvidia to add it and then if you prefer vscode as IDE click it and it adds etc and when you have choose deaults it starts to build/rebase on what you choosen i think this would help benefit alot of users as new/starting for atomics and less trouble shoots and learning for layers and containers at start since you just choose main apps on installer and then done start using and after that if/when need more you have options still to do and add more
Not exactly what youâre asking for, but you may be interested in Universal Blue.
yeah there are plenty of custom images to choose, but what i actually mean how awsome it would be to choose atomic and on installation process you can choose what to add as default so basically you can make your default custom with default apps already based on base no need to search and rebase just pick and choose what you need install and start working
Well point and click is just a reference and prob some future possible, but it is nice to have feature and will help many and glad there is already some work to achieve this great work already shame I donât have time or skills to even contribute only ideas for now
Will be waiting to see progress and test this some day
BlueBuild, which recently spun off from Universal Blue, may be what youâre looking for in the short-term while Image Builder is being discussed.
Yeah, ublue had an experimental ISO with boot options. You select a boot option and it does a netinstall. The result was veeery alpha though.
Then the status was, that the first ISO was improved, but now I cant find it anymore.
That bluebuild iso creator gave me some errors (already reported), lets see!
Their solutions always drive innovation further, Fedora is way more conservative.
It may be that Iâm misunderstanding your purpose, but this sounds kind of antithetical to the concept of Fedora Atomic Desktops. Derived images for specific uses is one thing, but I think if everyone ends up with their own personal base image, something has gone seriously wrong.
I do think there may be room for some sort of runtime extension system similar to systemd-sysext as an alternative to layering RPMs (and some of the less practical uses of containers). That could potentially allow the installer to offer a specific, curated set of âadd-onsâ.
Here what I mean is you have small amount of choose to pick up example if you are Nvidia end you can choose to build Nvidia drivers, then choose your default ide and that I mean getting VsCode to work as should including build in terminal functions that doesnât work on flatpaks what I last time trued to test and some small example if you are graphical user pick basic apps blender, inkscape, gimp etc and that way you just build your workflow install and start using rest what you need can be done on as now containers etc.
They say atomic is for lazy developers, but I see more work on setting it up after installation than if there is options to pick up on installation then install and start coding/working I donât mean there need to be everything but main base for IDE, Nvidia yes/no and some photo edit 3D programs etc to make your life faster and easier
NVIDIA is a non-starter because it canât be included in Fedora. My hope is that theyâll move to a unified kernel module with nouveau and people who want the proprietary driver will only need the userspace part, which can run in a container/flatpak.
To have a bunch of options in the installer, youâre talking about having 2n base images, layering packages in the installer, or generating a base image locally (which is just a worse version of layering). The least worst option of those is layering, but itâs still not great. Introducing client-side dependency resolution makes updates much more likely to fail and should always be done with intent.
The focus is on flatpak for graphical applications. Itâs true that most IDEs donât work well as flatpaks, but thatâs not an inherent issue. They âjustâ need to adapt their design for flatpak and containers as GNOME Builder has done.
Anyway, this whole concept is still baking. Weâll have to see what happens with e.g. ostree native containers in the future.
I am also not sure what bluebuild is doing there with that iso generator.