-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch rollback-helper to bootc switch #1913
Comments
Does |
If we did this, I'd imagine there would be logic to say "if the image has no layered packages, use Bootc. Otherwise rpm-ostree" |
I tried to implement the change and got an odd result testing it. If the command is run inside the However if I just do the same on the console, i.e. run Any ideas why this is the case? |
Likely you have some mangling of the tag or image.
…On Sat, Nov 9, 2024, 6:34 PM Malte Schmidt ***@***.***> wrote:
I tried to implement the change and got an odd result testing it. If the
command is run inside the ublue-rollback-helper script, I get the
following error message: ERROR Switching: Pulling: Creating importer:
failed to invoke method OpenImage: failed to invoke method OpenImage:
Requesting bearer token: invalid status code from registry 403 (Forbidden)
.
However if I just do the same on the console, i.e. run sudo bootc switch
ghcr.io/ublue-os/bluefin:41-20241109 myself it starts fetching the
image...
Any ideas why this is the case?
—
Reply to this email directly, view it on GitHub
<#1913 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQPNFFL74NBQ3F2CVACI6ULZ72LW5AVCNFSM6AAAAABRPKMZRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGUYDENBRG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Yes you are correct. I found the issue. |
bootc also tells the user what to do if you try to switch with layers. |
https://github.com/ublue-os/bluefin/blob/main/system_files/shared/usr/bin/ublue-rollback-helper
This should be using
sudo bootc switch ghcr.io/ublue-os/blah --enforce-container-sigpolicy
instead.The text was updated successfully, but these errors were encountered: