I have been using atomic as my daily for over a year at this point. I have gotten to the point to where I build my own registry and rebase fresh install off of that.
I had a crazy thought and not sure if it’s is possible but was hoping to get someone to chime in.
Would it be possible to add a Rebase registry URL or Custom registry URL When using the Anaconda installer?
Or would it be possible to have a “base image” iso as part of the Media Writer that allows a custom registry URL?
I’m just spitballing here, but I feel like something like this would be fantastic to be able to roll out a custom image without re-basing a fresh install.
Typing from mobile, so I apologize if formatting might be off a bit.
I’m not entirely sure if this is what you asking for, but it is entirely possible to create an ISO file, i.e. a disk image, from a customized Fedora Atomic Desktop Bootable Container image.
I’m aware of the iso creation with. I think it was ublue that makes the process?
I tried following their instructions multiple times you could never get a bootable ISO.
My suggestion or question would be to have the possibility to provide a OS tree image registry URL installer. I’m not 100% sure how os and initializes on first boot.
I’m thinking from the outside looking in I thought maybe it would be possible to provide a URL to rebase either your own silver blue image or Base atomic (depending on if base atomic can be even made in ISO)
Maybe it would be nice to have a official Fedora custom ISO process for atomic.. I have found both the ublue/bluebuild/bluefin documentation conflicting or missing steps. An official Fedora process in my eyes would probably have more adoption and be more widely accepted.
I still find that the atomic distros are still widely misunderstood and people don’t realize that you could create custom images using container files and then eventually Boot c
I am not closely familiar with the BlueBuild project and the image-template repo, but from what I know, they are used by many people and should be user-friendly and well documented. The Fedora/CentOS bootc project has good documentation that is applicable to Atomic Desktops Bootable Containers. However, to my knowledge, there is no complete guide or tutorial that explains the process of building a derived container image and creating an ISO file or other disk image, from start to finish. I think it is a good time to consider starting the preparation of such a document.
I been trying to pull the threads on all the little pieces on taking an oci and making an iso from it.
Your right, there isn’t a complete step/guide eon how this accomplished.
I don’t want to use bluebuild, and I’m sure wits great, I might just have to reverse engineer the process.
Is this something that would be included in the image-builder project I have seen mentioned a few times?
Thanks for your insight, I try not to blindly use other abstractions if it’s something I can do my self. Especially with a project like bluebuild that adopted it’s own opinions such as using a config file to add/remove packages/flat paks.
If you follow the Fedora/CentOS bootc docs from my previous post and the one provided here, you should be able to build a derived bootable container image and an ISO file from it yourself.
Though, I also think that a complete guide would be useful.
I would recommend using the following (still unofficial) images as a starting point. These images are also currently used by the Universal Blue Project.
!