Changing image base from Ublue images to vanilla Silverblue - what is the best approach?
Hi! I have a question, if I wanted to migrate my custom image's base from ublue's
I've tried doing so several times in the past w these steps:
1. Create a custom Silverblue image in my repo with
2. Builds just fine with the signing module
3. Update my existing result image recipe.yml (let's call this
4.
5.
6. When running rpm-ostree update, it fails giving errors as such:
Some digging around made me think perhaps it has something to do w/ files under
I wonder if it would be more efficient to just create a new repo altogether?
Would appreciate any input on this!
silverblue-mainI'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-silverbluebase-imagecustom-silverblue-base2. Builds just fine with the signing module
3. Update my existing result image recipe.yml (let's call this
result-imagebase-imageghcr.io/ublue-os/silverblue-maingchr.io/username/custom-silverblue-base4.
result-image5.
result-image6. When running rpm-ostree update, it fails giving errors as such:
Some digging around made me think perhaps it has something to do w/ files under
/etc/pki/containers/etc/containers/registries.d/sudo ostree admin config-diffI wonder if it would be more efficient to just create a new repo altogether?
Would appreciate any input on this!
Solution
Gave it another test - it seems like the following approach as I've described above, or simplified:
1. Create
2. Create
3. Deploy & continuously update/check for updates using
will give the
However, this approach works:
1. Create
2. Deploy & continuously update/check for updates using
works fine and doesnt' give me the parsing signature errors.
So for now I've resigned to making a
1. Create
custom-silverblue-baseREPO2. Create
result-imagecustom-silverblue-basebase-imageREPO3. Deploy & continuously update/check for updates using
rpm-ostree updatewill give the
Error parsing signature storage configurationHowever, this approach works:
1. Create
result-imagefedora/fedora-silverbluefedora-ostree-desktops/silverbluecustom-silverblue-base2. Deploy & continuously update/check for updates using
rpm-ostree updateworks fine and doesnt' give me the parsing signature errors.
So for now I've resigned to making a
base-recipe.ymlfrom-file: base-recipe.yml