UB
Universal Blue•2w ago
furkie

Unable to rebase from bazzite to bazzite-dx

It seems like I am unable to rebase to bazzite-dx, using the instructions found in this thread https://discord.com/channels/1072614816579063828/1362773232327065734 This is my rpm-ostree status output before the rebase attempt: 
State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
After running sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/bazzite-dx:stable, my rpm-ostree status looks like this: 
State: idle
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx:stable
                   Digest: sha256:1bf95e0b5050634cf06dc8193f15b22ba85fdec270f877bfd06f050325d88d05
                  Version: 42.20250417 (2025-04-19T04:03:10Z)
                     Diff: 46 added

● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
State: idle
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx:stable
                   Digest: sha256:1bf95e0b5050634cf06dc8193f15b22ba85fdec270f877bfd06f050325d88d05
                  Version: 42.20250417 (2025-04-19T04:03:10Z)
                     Diff: 46 added

● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
Solution:
I managed to solve it, and I am not sure why I didnt try it this way initially but I'll put it out there in case anyone else stumbles upon this and tries it the same way: Instead of running sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/bazzite-dx:stable, my rpm-ostree status like the other post is mentioning, I ran rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx:stable instead. ...
Jump to solution
2 Replies
furkie
furkieOP•2w ago
When rebooting, the bazzite-dx deployment doesnt show up in the grub menu and I am booted back bazzite, with rpm-ostree status now giving me: 
State: idle
Warning: failed to finalize previous deployment
         error: Finalizing deployment: Finalizing SELinux policy: Child process exited with code 139
         check `journalctl -b -1 -u ostree-finalize-staged.service`
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
State: idle
Warning: failed to finalize previous deployment
         error: Finalizing deployment: Finalizing SELinux policy: Child process exited with code 139
         check `journalctl -b -1 -u ostree-finalize-staged.service`
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
                   Pinned: yes

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
                  Version: 42.20250417 (2025-04-17T07:35:37Z)
Checking journalctl -b -1 -u ostree-finalize-staged.service gives me: 
Apr 21 22:16:19 kleindoosje systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 21 22:17:19 kleindoosje systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
Apr 21 22:17:19 kleindoosje ostree[4444]: Finalizing staged deployment
Apr 21 22:17:20 kleindoosje ostree[4444]: Copying /etc changes: 28 modified, 0 removed, 86 added
Apr 21 22:17:20 kleindoosje ostree[4444]: Copying /etc changes: 28 modified, 0 removed, 86 added
Apr 21 22:17:20 kleindoosje ostree[4444]: Refreshing SELinux policy
Apr 21 22:17:22 kleindoosje ostree[4444]: Refreshed SELinux policy in 1319 ms
Apr 21 22:17:22 kleindoosje ostree[4444]: error: Finalizing deployment: Finalizing SELinux policy: Child process exited with code 139
Apr 21 22:17:22 kleindoosje systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
Apr 21 22:17:22 kleindoosje systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'.
Apr 21 22:17:22 kleindoosje systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 21 22:17:22 kleindoosje systemd[1]: ostree-finalize-staged.service: Consumed 1.916s CPU time, 108.3M memory peak.
Apr 21 22:16:19 kleindoosje systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 21 22:17:19 kleindoosje systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
Apr 21 22:17:19 kleindoosje ostree[4444]: Finalizing staged deployment
Apr 21 22:17:20 kleindoosje ostree[4444]: Copying /etc changes: 28 modified, 0 removed, 86 added
Apr 21 22:17:20 kleindoosje ostree[4444]: Copying /etc changes: 28 modified, 0 removed, 86 added
Apr 21 22:17:20 kleindoosje ostree[4444]: Refreshing SELinux policy
Apr 21 22:17:22 kleindoosje ostree[4444]: Refreshed SELinux policy in 1319 ms
Apr 21 22:17:22 kleindoosje ostree[4444]: error: Finalizing deployment: Finalizing SELinux policy: Child process exited with code 139
Apr 21 22:17:22 kleindoosje systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
Apr 21 22:17:22 kleindoosje systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'.
Apr 21 22:17:22 kleindoosje systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
Apr 21 22:17:22 kleindoosje systemd[1]: ostree-finalize-staged.service: Consumed 1.916s CPU time, 108.3M memory peak.
Solution
furkie
furkie•5d ago
I managed to solve it, and I am not sure why I didnt try it this way initially but I'll put it out there in case anyone else stumbles upon this and tries it the same way: Instead of running sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/bazzite-dx:stable, my rpm-ostree status like the other post is mentioning, I ran rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx:stable instead. Interestingly, rebasing into ostree-unverified-registry:ghcr.io/ublue-os/bazzite-dx:stable will also fail with the same error, despite the sha256 digest being identical (which I'm assuming means I should be pulling an identical deployment).

Did you find this page helpful?