amel
amel
BBlueBuild
Created by amel on 2/14/2025 in #questions
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 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 3. Update my existing result image recipe.yml (let's call this result-image) - base-image is replaced from ghcr.io/ublue-os/silverblue-main to gchr.io/username/custom-silverblue-base 4. result-image builds just fine with the signing module 5. result-image is deployed just fine on the target machine, boots & runs as expected 6. When running rpm-ostree update, it fails giving errors as such:
Error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: Error parsing signature storage configuration: "docker" namespace "ghcr.io/username" defined both in "/etc/containers/registries.d/result-image.yaml" and "/etc/containers/registries.d/custom-silverblue-base.yaml"
Error: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: Error parsing signature storage configuration: "docker" namespace "ghcr.io/username" defined both in "/etc/containers/registries.d/result-image.yaml" and "/etc/containers/registries.d/custom-silverblue-base.yaml"
Some digging around made me think perhaps it has something to do w/ files under /etc/pki/containers and/or /etc/containers/registries.d/, but sudo ostree admin config-diff doesn't show that the files have been modified locally. Also, my cosign keys are unmodified, so this is not like the case of Bluefin's cosign keys from last year. I wonder if it would be more efficient to just create a new repo altogether? Would appreciate any input on this!
13 replies