amel
BBlueBuild
•Created by amel on 2/14/2025 in #questions
Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
I actually had
base-image and result-image on different workflows & jobs, so base-image being outdated wasn't a potential issue. IME the keys failing to parse happened all the time though, which is puzzling to me. It's no longer a problem bc I think the workaround works just as well, but I honestly am still a bit intrigued lol. Will give it another try when I have the free time (and motivation)13 replies
BBlueBuild
•Created by Jonathon on 2/16/2025 in #questions
Do I Include base packages in recipe such as ffmpeg and distrobox or are they installed by default?
The default
base-image in that template is ghcr.io/ublue-os/silverblue-main:latest, so yes it already has distrobox and ffmpeg. You can see the complete list here for that base image (and for other base images by ublue-os): https://github.com/ublue-os/main/blob/main/packages.json
If you choose to use vanilla Silverblue images as base, e.g. fedora/fedora-silverblue, then yes you will have to install them on your own using the template9 replies
BBlueBuild
•Created by amel on 2/14/2025 in #questions
Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
The 2nd approach works fine! It was probably an issue of the custom base image and the new/result image coming from the same repo hence having the exact same keys? Either way I've found a workaround!
13 replies
BBlueBuild
•Created by amel on 2/14/2025 in #questions
Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
Gave it another test - it seems like the following approach as I've described above, or simplified:
1. Create
custom-silverblue-base in REPO
2. Create result-image using custom-silverblue-base as base-image, also in REPO
3. Deploy & continuously update/check for updates using rpm-ostree update
will give the Error parsing signature storage configuration errors without fail.
However, this approach works:
1. Create result-image using fedora/fedora-silverblue or fedora-ostree-desktops/silverblue with a set of recipes that would have gone into custom-silverblue-base
2. Deploy & continuously update/check for updates using rpm-ostree update
works fine and doesnt' give me the parsing signature errors.
So for now I've resigned to making a base-recipe.yml that layers basically everything that will be shared across images (repo files, bling, codecs, layers/removals of unneeded fedora packages, extensions etc), and just from-file: base-recipe.yml it in multiple image recipes. I've only tested on one machine though, will give it another try on a diff machine13 replies
BBlueBuild
•Created by amel on 2/14/2025 in #questions
Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
Oh I've actually reverted to my
silverblue-main config as of right now LOL. I'll give more tries over the weekend to see if I can find out what's the possible cause, this isn't the first time I tried. This time I initially thought it was bc cosign pkg was missing during the initial switch from silverblue-main to silverblue base, but running custom-silverblue-base on Boxes gives no problems and it updates just fine.
Will update here more once I've gone back to the silverblue base config. Or yeah I guess I'll just eventually build a new repo13 replies