It doesn’t seem like osbuild could generate that
It doesn’t seem like osbuild could generate that
AThere’s also cockpit-composer
GGenerate a multi-netinstall?
AYeah
AMaybe there’s a way of passing a custom grub menu
AThat’s all we really need
GI'm sure there's something
G
G
Gcan't run it in a rootless container
Ggonna have to be a rootful with with systemd most likely
Gor a VM
ARootless —privileged kinda works except the socket for whatever reason doesn’t
AHuh doesn’t work rootful either
A
Acockpit-composer looks very nice
Ghonestly
Git could be cool
Gif we switched to osbuild for composing OCI images
Gbecause we can do that
Aeh, it means we can't derive in that from fedora from what i can tell
Gtrue
A
GGist
Scripts to create custom fedora silverblue iso. GitHub Gist: instantly share code, notes, and snippets.
Gwonder if this could be adapted to make a local install image
AIf you know how to use Lorax, yeah
ALorax is how fedora makes their isos
Jthis would still be very useful for bazzite, bluefin, custom images etc. where having one ISO makes sense
Jstill though, if 19 ISOs come out of an action I'd love to see that just to see it lol
Jand also github has a releases file size limit, so we'd have to find another way to distribute them
ADo like akmods and put the iso inside a container I guess
JI can get donated CDN bandwidth too, but that can come later
Jif we can figure out more reliable ISOs with the new installer it would immediately fix the least reliable part of the project. 
AYeah we need to get off the business of binary patching fedora ISOs...
Gthey are switching to osbuild though
Gat least there's a proposal to switch osbuild on workstation
AYeah
AAll we really need is to generate a boot iso with custom grub and kickstart file
For offline installers we'd have to replicate the fedora process
For offline installers we'd have to replicate the fedora process
Jare you checking out osbuild? it's been on my todo but I'm about to start travelling a bunch for work and my free time is going away
Git looks really easy to make a simple netinstall image
Gthis was the command
ADoes that require an ostree repo?
Goh
Git might
Git shouldn't, since they are switching to OCI in Fedora 39
BI'm looking into https://github.com/ublue-os/config/issues/26 regarding adjusting the timers for both flatpak update timers and rpm-ostreed-automatic timer
BI want to add our own copy of
/usr/lib/systemd/system/rpm-ostreed-automatic.timer but it's owned by the rpm-ostree RPM... so... not sure how i want to modify it's contents ...Bcurrently we just enable it here https://github.com/ublue-os/main/blob/main/post-install.sh#L5
Bi think i'll add a copy of what we want in our version in the ublue-os-update-services RPM at
/usr/share/ublue-os/update-services/etc/systemd/system/rpm-ostreed-automatic.timer and then copy it into place and enable it just like we already do here https://github.com/ublue-os/main/blob/main/post-install.sh#L5-L10G@j0rge looked at the github issue and found this comment: https://github.com/coreos/fedora-coreos-tracker/issues/1151#issuecomment-1351656773
GitHub
This is touched on in https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md#use-of-coreos-diskboot-images Basically I think our default stance is that admins use our golden images ...
