Hi there,
having used Aurora for more than a year now, I have some things that are not working properly. E.g. my laptop always wakes up when I connect the power plug and I cannot seem to get to work my wifi printer.
Therefore I wanted to see if these thing work in Kinoite. I found a tutorial on how to rebase from Kinoite to Aurora. But how do I do this the other way round (from Aurora to Kinoite)?
That way I could try and see if the above problems also exist in Kinoite.
Regards
Stephan
You should be able to just run
sudo bootc switch quay.io/fedora-ostree-desktops/kinoite:43
If you want to check what would change before switching you should be able to run:
sudo bootc switch --retain quay.io/fedora-ostree-desktops/kinoite:43
Then run rpm-ostree db diff to see what would change if you rebooted. If you don’t like what you see, you can run sudo bootc rollback before rebooting.
If you have layered packages installed via rpm-ostree install, they may or may not carry over. You could do a sudo rpm-ostree reset to uninstall anything you installed using rpm-ostree install before doing the bootc switch if you are worried about that.
Thanks a lot! This worked.
Unfortunately, my problems are not solved in Kinoite. Therefore I switched back to Aurora (via Grub).
By the way: how can I switch back to a previously pinned version (via sudo ostree admin pin 0)?
You should be able to just do sudo bootc rollback which will set the prior version as the default boot target. You have to reboot to actually make it happen.
You could run bootc status or rpm-ostree status to show versions available to you and confirm that a bootc rollback gets you to the image you want.
You will probably want to eventually unpin the image you pinned as it won’t automatically be garbage collected (so it stays available after multiple updates).
Hi thanks for the info here. Do you have any idea how to get back on a verified Fedora Kinoite image? I am not sure if Aurora turns off image verification but when I ran this command, I am now on:
â—Ź ostree-unverified-registry:quay.io/fedora-ostree-desktops/kinoite:43 (index: 0)
Have you tried rpm-ostree rebase ostree-image-signed:docker://quay.io/fedora-ostree-desktops/kinoite:43 ? That seemed to work for me pulling a new image (I tried it with the --download-only switch to try a dry run without deploying.
I did try that but it gave error:
error: Switching: Switching (ostree): Preparing import: Fetching manifest: containers-policy.json specifies a default of `insecureAcceptAnything`; refusing usage
And this cascades into a whole plethora of errors. You can change /etc/containers/policy.json to reject instead of insecureAcceptAnything, but then you get another error because there are no keys or registry:
error: Preparing import: Fetching manifest: failed to invoke method OpenImage: Running image docker://quay.io/fedora-ostree-desktops/kinoite:43 is rejected by policy.
And that’s where my search for an answer falls apart
I’m sorry my advice didn’t work for you. Perhaps our base systems are too far apart. I’m on a custom Fedora Kinoite image (https://github.com/whelanh/myKinoiteNightly) which I rebased to first using the unsigned image and then the signed image. You could try rebasing to my unsigned image, then signed image, and then to a signed “stock” Fedora Kinoite…but I have no idea if that strategy would really work to straighten out your policy.json and get you the right keys/registry.
No problem! Thanks for trying! It seems like it may be because I am still on OCI containers which are unofficial. (even though you said yours works somehow). Even if I could sign the container, I do not want to use them because system auto updates won’t work with KDE Plasma unless you are on standard ostree images right now as far as I can tell.
I think I’m just going to reinstall with Kinoite ISO. Hoping most of settings migrate with my home folder.
Honestly a re-install is what I would do also in your position. Best of luck with the settings migration! 