cant connect to docker daemon on bazzite
how am i expected to run docker for building isos with bluebuild on bazzite?
Solution:
-R podman
Labels and metadata
Hello! I am looking to add additional Lables to my container and overwrite labels that are coming from the template in bluebuild-cli https://github.com/blue-build/cli/blob/main/template/templates/Containerfile.j2. It adds
I would like to set this to my own readme along with the rest of the artifacthub labels as outlined in this open issue: https://github.com/blue-build/cli/issues/342....
LABEL io.artifacthub.package.readme-url=https://raw.githubusercontent.com/blue-build/cli/main/README.md
LABEL io.artifacthub.package.readme-url=https://raw.githubusercontent.com/blue-build/cli/main/README.md
Auto updates
Hey, it's my understanding that ublue images come with auto updating configured out of the box.
I can see that my GH actions have successfully gone off, there is a new
latest image, but I haven't gotten any updates pending.
rpm-ostree status does show that the automatic update timer was last run 11m ago.
...What is the difference between rpm-ostree and dnf modules?
I understand that one installs packages using dnf5 and the other does so with rpm-ostree, but I have trouble understanding when I would want to use one over the other. Does one or the other perform better for solving certain problems? If so which ones?
Solution:
rpm-ostree was the "original" module, and after that dnf is added
Error: creating build container ... no signature exists
Getting this error trying to build my recipie
...
Error: creating build container: unable to copy from source docker://ghcr.io/ublue-os/silverblue-main@sha256:6faa4fbddb138b907bbd2623de45f27a554249b09eb765a2c0eac42927c626bd: Source image rejected: A signature was required, but no signature exists
Error: creating build container: unable to copy from source docker://ghcr.io/ublue-os/silverblue-main@sha256:6faa4fbddb138b907bbd2623de45f27a554249b09eb765a2c0eac42927c626bd: Source image rejected: A signature was required, but no signature exists
Solution:
Hmm, all that is still set to the defaults. That didn't seem to be the culprit though, my problem is more that podman couldn't determine if the image was signed. Not sure if this means that podman couldn't find the public keys listed in the policy or what, but after a podman system reset, this does seem to be working
Adding "post-install" programs that aren't part of the image
Hey, just getting started with fedora silverblue and discovering bluebuild. I'm trying to still build up an understanding and approach of where things should go.
The intro docs say resist the urge to add the whole universe (https://blue-build.org/learn/mindset/#resist-the-urge-to-add-the-entire-universe), so my question is what's the approach to handling those other flatpaks, etc. Is this something people would use justfiles for? Something else? Or do you just install those by hand once and hope you don't need to do it again? Coming from nixOS if that helps....
The intro docs say resist the urge to add the whole universe (https://blue-build.org/learn/mindset/#resist-the-urge-to-add-the-entire-universe), so my question is what's the approach to handling those other flatpaks, etc. Is this something people would use justfiles for? Something else? Or do you just install those by hand once and hope you don't need to do it again? Coming from nixOS if that helps....
nvidia akmod
Hi I've read the doc at - https://blue-build.org/reference/modules/akmods/
I've looked for examples from others through their github
I've asked chatgpt and tried a lot of things but I just can't get the syntax right for the nvidia akmod install.
this is what I currently have in recipe.yml;
` - type: akmods...
Issues with rebasing
So, I've managed to build an ISO with my custom image and have gotten it to boot in a VM, but when I try to rebase to said image from bluefin it won't boot when i try. Does anyone know what could be causing that?
repo link: https://github.com/Synby-OS/Synby-OS...
default-flatpaks module jams up on simple recipe
Hey folks!
I'm having some difficulty with the
default-flatpaks module not automatically kicking in, and when I try doing bluebuild-flatpak-manager apply all, I get an error back that makes little sense to me.
My repo: https://github.com/BrodyB/FedoraGDX...
Build Errors
Not sure what happened, but my Github action started failing today. Seems to happen after fetching the JSON schemas.
```
[17:31:37 DEBUG] => Logged into ghcr.io
logged in via /home/runner/.docker/config.json
[17:31:37 DEBUG] => Logged into ghcr.io...
Error building: "Not authorized: url"
got this error at the very end of the build process. my image seems to have been pushed properly but with this happening idk. anyone know what's causing it?
repo: https://github.com/Synby-OS/Synby-OS...
Solution:
verify that github actions can access packages, and you need to make them publicly available
Adding large files to an image via Git LFS
I have been working on a custom image, and want to drop a bunch of my favorite hi-res images into
/usr/share/wallpapers. So I put them in my repo with a files module and committed them using Git LFS to avoid directly committing large binaries.
However, when I run my build, Blue Build just writes the symbolic link for each large file into the wallpapers directory instead of the actual file.
I tried setting up LFS in my image using a script module , and have considered writing a custom module to handle LFS. But it seems that, because module seem to run within the context of a Containerfile, it does not recognize that it is even in a Git repo. ...dnf packages not removed on my final image
I'm running into an issue where some of my package listed in the
remove section of the dnf module are still in my final image.
I suspect that it's because these packages (fuzzel, alacritty and waybar in my case) are installed as a dependency of another package listed in the install section.
I wonder if there is a way to run the remove section after the install section as a workaround for this issue.
Another way would be to track down where these packages come from. I couldn't with just the bluebuild action logs, but I strongly suspect it is shipped with the niri package, I would appreciate it if someone can guide me to track down these packages (I don't really know much about rpm packaging ...)
...Solution:
For reference https://github.com/blue-build/modules/pull/462
nfs file sharing not working with bazzite bluebuild custom
I tried using nfs server and received the error mount.nfs: mounting 192.168.1.124:/nfs-share failed, reason given by server: No such file or directory. I decided to set up a nfs docker image with podman as an alternative and with the help chatgpt i did a lot of troubleshooting. The container should work just like the native nfs package but it doesn't. The same error occurred from the client. Has anybody got nfs working with bazzite? From my point of view i have a broken system.
Display managers not starting
I've tried both GDM & LightDM both of which just freeze before displaying
```yaml
---
name: brokenone
description will be included in the image's metadata...
Installing from local rpm packages?
Can I install a local .rpm with bluebuild or is this not possible and/or bad practice?
Solution:
That works and is supported, take a look at the documentation for the dnf module:
https://blue-build.org/reference/modules/dnf/...
Language Server Protocols
Sinmce some people here are using LSPs with their favourite editors, I wanted to ask what's the best way to install them? Do you just add the packages, use them in a distrobox or from brew?
Best way to pin Nvidia drivers to specific version
Hello, the latest nvidia drivers make my entire desktop crash when closing GTK apps, and I want to pin it to the previous version. What would be the simplest / recommended way to do this (I still want to receive updates for other things)?
Solution:
ill just wait for the new driver release and keep the image version pinned
Recommended unattend install method for BlueBuild images?
I would like to do a bare metal install on my computers using a custom image built with BlueBuild and have it be completely unattended. Right now I can build an ISO image and write it to a USB drive per documentation. But being relatively new to the Fedora ecosystem, I'm not sure which tool(s) I should be using to a) create the user account info and b) how I can inject or side-car that info into the installation process.
I've used cloud-init in the Ubuntu space. Not sure if that's relevant here. Searching has also turned up Ignition/Butane and Kickstart. It's not clear to me which tool is the best fit for this job.
I tried using Butane to generate an ignition file, and then tried to inject that into the ISO using coreos-installer, but that last part failed - unsurprisingly - since I'm building a Aurora based image....
Solution:
Ultimately the answer for Aurora (which I was customizing): Create an ISO / image / USB drive with a volume label of
OEMDRV and place the Kickstart file named ks.cfg in the root of this drive. Anaconda based installers look for a volume of this label by default and will pick up the Kickstart file automatically. To generate a good starting point for the Kickstart file, you can do a manual install first and then grab the generated file from that install process at `/var/roothome/anaconda-ks.cf...setup on Gitlab with build --push: how to extract files from local image?
I jump through several loops to get my images scanned with trivy and data visualised with gitlab.
1)
trivy image fails to scan because the rpmdb.sqlite is in the wrong place and trivy does not follow symlinks: https://github.com/aquasecurity/trivy/discussions/9188#discussioncomment-14162815
2) I run rpm -qa in the image and pipe the output outside the image to construct an SBOM file that can be read with trivy sbom...