containers / bootc

Boot and upgrade via container images
https://containers.github.io/bootc/
Apache License 2.0
789 stars 84 forks source link

Unable to bootc switch again after migrating silverblue to fedora-bootc #855

Closed Perpixel closed 1 week ago

Perpixel commented 1 month ago

Hello, not sure if this is working as expected, but I'm trying to test migration from a rpm-ostree Silverblue system to bootc on a qemu vm before doing it to my own workstation.

My system seems now stuck with only 2 deployments of fedora-bootc 40 and 41.

The documentation is not super clear on the right path to take to make this transition, so maybe it's just me?

Thanks

Perpixel commented 1 month ago

Just did the same step again on a clean VM, and now it works... Only this time I started from Silverblue:41

Perpixel commented 1 month ago

I was able to repro this if anyone interested. On reboot it probably fail in the deployment and reboot because I got a grub selection screen.

Image Image

ryanabx commented 1 week ago

I'm also curious about this. Is there documentation about the recommended migration path from non-bootc managed images to bootc images?

ryanabx commented 1 week ago

@cgwalters I noticed https://github.com/containers/bootc/pull/137 recently got merged. Is the intended migration for existing ostree systems to use --replace-mode=alongside?

cgwalters commented 1 week ago

I'm also curious about this. Is there documentation about the recommended migration path from non-bootc managed images to bootc images?

We want it to basically just be switch. I think what you're running into here is basically https://bugzilla.redhat.com/show_bug.cgi?id=2308594

@cgwalters I noticed https://github.com/containers/bootc/pull/137 recently got merged. Is the intended migration for existing ostree systems to use --replace-mode=alongside?

That's related for sure, but a bigger hammer as it will reset more things.

Anyways so I think this is a dup of https://github.com/containers/bootc/issues/632