BlueBuild

B

BlueBuild

Join the community to ask questions about BlueBuild and get answers from other members.

Join

I can't use rechunker in GitLab?

I'm trying GitLab this time instead of GitHub. While rechunker seems to work fine in GH side, I can't say the same for GitLab. https://gitlab.com/vedaproject/vedaos/-/jobs/11020875701#L171 Isn't it trying to open yet another Docker instance on top of Docker-Docker?...

kargs module not working for me

Weirdly enough, the kargs module seems to not work properly for me. It creates the file in /usr/lib/bootc/kargs.d/bluebuild-args.toml and then i upgrade with bootc. But after a reboot, it didn't stick. I saw it working one time for sure in the last week, but right now bootc seems to ignore it for some reason

i need help to build an image with a default fedora image (like the sway atomic)

the ublue-main image wont play nice with my image, but building the image with a defauly fedora image wont really work properly

Installing SDK with multiple branches as default flatpak

Hey, Got a question about installing an sdk with different branches as a default Flatpak app using Bluebuild. I've tried to add org.freedesktop.Sdk.Extension.texlive to my default-flatpaks list, but then it doesn't install this. ...

gschema module not applying overrides consistently

I've been trying to work with the gschemas module and not seeing my overrides working consistently. I've followed the documentation closely to make sure I was doing everything as outlined. For example, on my resulting image, I find that the setting for preferring Dark Mode worked, but the settings for tap-to-click and custom keyboard shortcuts didn't. I started with a fresh install of plain-old-Silverblue, and didn't change any settings by hand. Am I doing something wrong, here? https://github.com/BrodyB/FedoraRemix/tree/main/files/gschema-overrides...
Solution:
Actually, solved it. The issue was there being minor syntax errors with my gschema that didn’t fail out the module. Fixing those let it go through just fine!

can't override /usr/lib/waydroid/data/scripts/waydroid-net.sh

I'm trying to change the LXC_USE_NFT variable to "false" since that seems to solve the network issue i'm having (cannot turn on wifi on waydroid). I have a file on my recipe to override the default waydroid-net.sh but when I reboot it still has LXC_USE_NFT="true"

Default Flatpaks not installing?

Hey, I just tried out to run my own spin using BlueBuild. Everything works great, however it seems the default Flatpaks I specified are not installing. This is the case both for my regular system which was already set up, but also when I built an ISO and installed that in GNOME Boxes. Packages that I defined to be installed in rpm-ostree work fine. The interesting thing is that the GitHub Action does seem to handle the flatpaks, as I did get an error when I pointed to a flatpak from the fedora repository (it's not on Flathub with that name, so it couldn't find it). So it's not like the default flatpaks are ignored. ...
Solution:

default-flatpaks v2 migration issue

I updated my default-flatpaks config to use the new module, but my builds fail. ``` [12:02:20 ERROR] => Failed: × Recipe ./recipes/ptinopedila-home-nvidia.yml failed to validate ╰─▶ × 1 error encountered...
Solution:
First key under "configurations:" needs "-", as its an array, you're missing that since you commented out the notify line

ujust error

ndowens@Revan ~ [127]> ujust You must run ujust inside a container I've searched bazzite's code and general web search and have not figured out where the error is coming from. I have also asked in bazzite's discord channel but seems no one can help me there either....
Solution:
what base image? and what is the output of which ujust?

Enabling lingering at build time ?

Hi bluebuild team, I wonder if there is a way to enable lingering for specific users at build time ? (I would like to do so to start the niri.service service in systemd/user automatically at boot)

Building x86_64-v2 instead of x86_64-v3

Hi all, hi @Luke Skywunker ! For my https://eu-os.eu project, I switched to AlmaLinux packages. They build by default for arch = amd64v3. On old hardware (think of schools), this does not run anylonger. Also not on my Thinkpad x220 test device. A PR is open to build the bootc image for amd64v2 as well. https://github.com/AlmaLinux/atomic-desktop/pull/38 It seems to me that bluebuild does not expose the --arch flag from podman, so I do not see how I could force bluebuild to pick one x86_64 over the other (unless I build on a device with only v2 support)....

formatting

ive tried to fix my code and yet it wont work

Error in the Daily BlueBuild Job on the Files Module

The scheduled bluebuild job that came with the template, starting failing on the files module on July 1. It looks to be because of a missing directory. Is this a Module error or my configuration? Job Error [06:23:15 g.i/c/cit-os:latest] => #44 0.093 ============================= Start 'files' Module =============================...
Solution:
That's a bug, let me see if I can fix it real quick

Zen browser install id doesn't exist in flathub repo

i dont know why it isnt working, ive put the correct flatpak name [16:41:20 g.i/v/kami-os:latest] => 0.830 ERROR: This system install flatpak ID 'org.zen_browser.zen' doesn't exist in FlatHub repo, please check if you typed it correctly in the recipe....
No description

would yall have any idea as to why im getting the following conflict after having added Terra?

``` [15:45:35 g.i/a/morrigan:latest] => 75.17 Transaction failed: Rpm transaction failed. [15:45:35 g.i/a/morrigan:latest] => 75.17 - file /usr/lib64/libastal-io.so.0.1.0 conflicts between attempted installs of astal-io-libs-0^20250629.ac90f09-1.fc42.x86_64 and astal-io-0~6.git7f2292f-1.fc42.x86_64 [15:45:35 g.i/a/morrigan:latest] => 75.17 - file /usr/bin/astal conflicts between attempted installs of astal-0^20250629.ac90f09-1.fc42.x86_64 and astal-io-0~6.git7f2292f-1.fc42.x86_64 [15:45:35 g.i/a/morrigan:latest] => 75.19 External command had a non-zero exit code...

Conflicting Nvidia driver packages

Haven't changed my build recipe in quite a while so I expect some part of what I have isn't necessary. I'm installing the following which I did after looking at a couple other people's builds: ``` - type: dnf...
Solution:
The error messages suggest that the package is already installed and does not need to be listed in my recipe

How to avoid 6 minute gap in build?

``` [17:24:33 INFO] => Retrieving OS version from ghcr.io/ublue-os/aurora-dx-hwe:42 [17:24:36 DEBUG] => Successfully inspected image ghcr.io/ublue-os/aurora-dx-hwe:42! [17:24:36 WARN] => Failed to parse version: Failed to deserialize version latest-42.20250627.2...
Solution:
Unfortunately, this is becuase upstream is changing the version string on the LABEL. We've had several people come and complain, but the reality is that if the LABEL on the image doesn't set the version properly, then we have to get that information from within the image which requires downloading it and running it. For docker builds, we make use of buildx which is a builder that runs in a container and unfortunately the docker frontend doesn't allow us to run arbitrary commands like `dock...

Build failure migrating from `rpm-ostree` to `dnf`

I feel like I'm missing a simple step for enabling the dnf module (migrating away from rpm-ostree). My builds are failing due to: chmod: cannot access '/tmp/modules/dnf/dnf.sh': No such file or directory Anyone seen this kind of error before?...
Solution:
you have a dependabot PR waiting that will also do this change for you https://github.com/michaelhaaf/bluebuild-custom/pull/11

Access tag/version from script module

Dears, In a container file, I run a command to set the /etc/os-release file. I can do this with the files or script module of blue-build. If I want to set the VERSION to the currently build tag of blue build, I guess I have to use the script module. Can you tell me how I can access in such scripts the version tag? This is how the file looks like for fedora kinoite:...