Error when trying to rebase to Bluefin from Silverblue (Failed to invoke skopeo proxy method)

Bluefin and Aurora
1

I have a laptop with both Fedora Silverblue and Windows 10, each in a separate SSD. I’d like to try bluefin, but had some issues trying to rebase to it.

I have uninstalled all my additional packages, and reseted my home directory.

I also “enrolled” the security key since I have secure boot enabled as I was instructed to do in reddit.

However when I try to run the command:
rpm-ostree rebase ostree-unverified-registry:docker://ghcr.io/ublue-os/bluefin-dx:latest

I get the following error message:

$ rpm-ostree rebase ostree-unverified-registry:docker://ghcr.io/ublue-os/bluefin-dx:latest
Pulling manifest: ostree-unverified-registry:docker://ghcr.io/ublue-os/bluefin-dx:latest
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: invalid reference format

I’m aware that the preferred method of installation is through and ISO, but I have a dual boot system that was set up for me. I’m a noob and I’d prefer not touching anything that could mess with my Windows partition.

Is there something I could do to be able to rebase into Bluefin? I already have a backup of my information. My CPU and GPU are both AMD.

2

As far as I know, this is the correct command:

rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bluefin-dx:latest

Then reboot & rebase to the signed version:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
3

Thanks! Those commands worked.

The only thing is when I choose Bluefin in GRUB before it starts loading it shows me a failure message for a couple seconds. It reads:
“[FAILED] Failed to start systemd-modules-load.service - Load Kernel Modules”

The message doesn’t appear if I choose to boot into Silverblue. Do you know if that’s something I should worry about? Besides that everything seems to work fine

4

Bluefin probably comes with additional kernel modules and one or more failed to load, causing the service to fail.

You could check the logs after boot and find out what module(s) failed to load. Try this:

journalctl -b -u systemd-modules-load.service

I probably won’t be able to help you further though, as I don’t use Bluefin.

5

No problem, thanks! I’ll try that

6

This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.