Preinstall appimage
How to add ujust setup-virtualization to recipe?
BlueBuild Image Build Failing

Do I Include base packages in recipe such as ffmpeg and distrobox or are they installed by 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 template...Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
silverblue-main
to Fedora's vanilla Silverblue, what would be the best way to do so successfully?
I've tried doing so several times in the past w these steps:
1. Create a custom Silverblue image in my repo with quay.io/fedora/fedora-silverblue
as base-image
. This creates custom-silverblue-base
2. Builds just fine with the signing module...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....Skip Failing COPR Packages?
--skip-broken
flag exists in dnf but I'm not sure how I would achieve the same behavior in BlueBuild.invalid reference format for aurora-dx
v0.9.5
and also v0.9.7
```
INFO => Recipe ./recipes/recipe.yml is valid
INFO => Templating for recipe at ./recipes/recipe.yml...Flatpak setup service failing and computer boots up to blank screen
What works on bootc images?
What is the proper format for installing an akmod in the recipe.yml ?
Making F41 Surface Images
Installing akmod with the correct kernel version
Issue with default Universal Blue update service (ublue-update.service)
Correct way to use custom image - rebase or install via ISO - UBlue "after boot" customizations?
Building ISO from custom Blue Build images based on Aurora - boots as Fedora Base 41
ghcr.io/mygithubacc/myaurora
package with all standard aurora stuff as well as my custom ones.
But when I build IOS from this as sudo bluebuild generate-iso --iso-name weird-os.iso recipe recipes/recipe.yml
(version 0.9.6) , it works, but when I install it and boot this image, it shows as Fedora Base 41 and rpm-ostree status output is quay.io/fedora-desktops/base:41
instead of expected ghcr.io/mygithubacc/myaurora
. So updates are not working etc. But on the other hand aurora customizations are in place, my custom packages from myaurora
are also there. Just the "source" address is pointing to wrong image. What I am doing wrong with the build? ...Date tags
Gitlab CI: update images automatically
AKMOD Displaylink (evdi)
I wanna rebase from ublue bluefin to wayblue hyprland
What does the uBlue Kinoite image come with by default?