Can no longer upgrade F43 Silverblue bootc

Ask Fedora
, , , ,
1

Running into update troubles with Silverblue
About a month ago, I rebased to the bootc base images using the following

rpm-ostree rebase ostree-unverified-registry:quay.io/fedora/fedora-silverblue:43
rpm-ostree rebase ostree-remote-registry:fedora:quay.io/fedora/fedora-silverblue:43

Current output of rpm-ostree status

kenryo@kendesk:~$ rpm-ostree status
State: idle
Deployments:
● ostree-remote-registry:fedora:quay.io/fedora/fedora-silverblue:43
                   Digest: sha256:56187cbebad4c81a870df99fdc1415382c4ef6945f5ec9445a2fa35ead048f7d
                  Version: 43.20251107.0 (2025-11-07T00:40:01Z)

Upgrades have been fine until today… now I get the following error when upgrading.

kenryo@silverblue:~$ rpm-ostree upgrade
Pulling manifest: ostree-remote-image:fedora:docker://quay.io/fedora/fedora-silverblue:43
Importing: ostree-remote-image:fedora:docker://quay.io/fedora/fedora-silverblue:43 (digest: sha256:a08df8fda0e40d3dc4675f62aec642e8f21e9628c13159fcd27137786d5bfdcb)
ostree chunk layers already present: 64
ostree chunk layers needed: 1 (5.7 MB)
[0/1] Fetching ostree chunk b346b7f83fb138fdeae (5.7 MB)... done
error: Importing: Unencapsulating base: Importing commit: Using remote fedora for verification; Expected commitmeta object, not DirMeta
2

I don’t know what would cause this error, as I’m not using images from the official Quay repo.

If you want to use the Atomic Desktops Bootable Container images, I would recommend the following instructions:

Also, to your question in the Fedora bootc Matrix room: These images are “unofficial” only because they are built outside of the Fedora infrastructure. They are maintained by the Fedora Atomic Desktops Special Interest Group (SIG).

You can also join Fedora Silverblue Matrix room if you haven’t already.