Do I Include base packages in recipe such as ffmpeg and distrobox or are they installed by default?
GitHub
GitHub - ublue-os/image-template: Build your own custom Universal B...
Build your own custom Universal Blue Image! Contribute to ublue-os/image-template development by creating an account on GitHub.
Solution:Jump to solution
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 template...13 Replies
Solution
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 templatethanks
Also just fyi: The ublue-os/image-template doesn't come with blue-build, that's just a containerfile. If you want to use blue-build (what this discord server is about), check out the docs https://blue-build.org/learn/getting-started/
BlueBuild
Getting started
BlueBuild is a collection of tools and documentation for making custom images of image-based Linux distributions.
Ok thanks will check it out
When i add bling, negativo17 repository https://negativo17.org/repos/multimedia/fedora-41/x86_64/ packages are not available in toolbx when i type dnf repolist. Is this mean't to be that way?
- type: bling
install:
- negativo17
Yes, because toolbx system is separated from the OS
so you just need to add negativo to toolbx manually
Ok cheers
What is the URL for the vanilla base repository for silverblue that you mentioned? ghcr.io/fedora/fedora-silverblue?
quay.io/fedora/fedora-silverblue
or quay.io/fedora-ostree-desktops/silverblue works toook trying it now thanks
What about signing? Do i just remove - type: signing # this sets up the proper policy & signing files for signed images to work fully
See https://blue-build.org/how-to/cosign/ for more information.
If you don't want to sign your image, use the
[01:15:34 ERROR] => Failed:× Unable to find private/public key pair help: Make sure you have a
./cosign.pub
in the root of your repo and have either COSIGN_PRIVATE_KEY
set in your env variables or a ./cosign.key
file in the root of your repo.
See https://blue-build.org/how-to/cosign/ for more information.
If you don't want to sign your image, use the
--no-sign flag.
Error: Process completed with exit code 1.you have to generate a cosign key first, commit, then you can use the signing module
you're also supposed to set up cosign even if you were to use ublue base images as far as i understand
but if you don't want signing yes remove
type: signing and use the --no-sign flagthanks