"A signature was required, but no signature exists" when trying to rebase to Bazzite DX
I used my custom image before, but now when I try to upgrade I get this error. What do I need to do?
EDIT: the problem was the lack of signature in the images themselves, we need to wait for the problem to be fixed (https://discord.com/channels/1072614816579063828/1367741029326782484/1367790632776499241)
EDIT #2: fixed!
38 Replies
I even downloaded the key from the repo, still no help
It would be nice if I could resolve it without reinstalling the system
output of
rpm-ostree status would be helpful
before the rebase to bazzite dx I was on my custom image, like I said earlier, then I couldn't upgrade in any way. rebase to regular bazzite was successful, after that going back to bazzite dx was not possible giving the same error
you may need bazzite.pub key
check
/usr/etc/containers/policy.jsonhuh, I didn't know there was a duplicate
but even so, I can't edit it
you can check every etc default there
dont edit, copy to current /etc
same error
whats the content
is it using bazzite-dx.pub?
not anymore
ok now does bazzite.pub exist?
in the path defined in the policy
nope, it was never there. the defaults defined in policy.json are
ublue-os.pub and ublue-os-backup.pub.
to clear up the confusion, bazzite.pub never existed in /etc/pki/containers, neither did bazzite-dx.pub. I downloaded the key from dx repo and put it in that folder hoping that would help, but nahI can't even rebase to unverified registry wth
what exist inside /usr/etc/pki/containers
huh
does bluebuild break anything that causes this to happen?
shouldnt be
i also build my custom image with bluebuild but bazzite.pub did exist in my usr folder
it's probably your custom image's key, not the official one. I had something like bazzite-nvidia-open.pub too cuz that's what I named my system in recipe
possibly
btw what is your current policy key
ublue-os.pub and ublue-os-backup.pub?
yeah
maybe best for me to just reinstall the system, going to take some time tho. not sure what to do at this point
if you dont have the time sure, but it might worth debugging and have solution for people in the future
or maybe there is actually bug in the image
oh wait, you're right
I took a different tag instead of stable, and it started downloading normally
not sure what happened then
huh, lemme see if i can repro this inside vm
fun stuff lol, latest image all skip signing step :KEKW:
so it wasn't just me then
btw you probably should file an issue in the dx repo https://github.com/ublue-os/bazzite-dx/issues
GitHub
Issues · ublue-os/bazzite-dx
The Bazzite Developer Experience. Contribute to ublue-os/bazzite-dx development by creating an account on GitHub.
Is there any fix for this right now? I also can't update
i dont think there is any fix yet, but technically you can just edit policy to accept everything (very insecure)
So is it just that the images aren't getting signed for some reason?
yes
yeah, you'll have to wait for now
https://github.com/ublue-os/bazzite-dx/issues/70 done. completely forgot about it
GitHub
The latest images are not signed, giving an error when updating/reb...
When trying to upgrade or rebase from the regular image, this error appears: $ brh rebase bazzite-dx-nvidia-open:stable Rebasing to ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx-nvidia-o...
Solution
@Lumaeris it's fixed now! signature is published again
@funky ^