-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error setting up sysroot: Missing base image" error on a custom image #392
Comments
Also hit this today, but only on my virtual machine install. After it errors, rpm-ostree also breaks. Same errors as in Jorges post. |
Looks like a dup of coreos/rpm-ostree#4185 which should be fixed by ostreedev/ostree-rs-ext#432 Updating in coreos/rpm-ostree#4203 - I'll post some bits on how to un-wedge things. Can you both confirm that you were doing client-side package layering i.e. |
I can confirm that I was layering client side on top of a custom image. |
Confirming I also encountered this yesterday in a VM. |
Yes i had few packages layered top of the image on the VM |
OK, I did coreos/rpm-ostree#4204 and ostreedev/ostree-rs-ext#436 - will get these PRs merged soon and then we'll have a build in https://copr.fedorainfracloud.org/coprs/g/CoreOS/continuous/ that should be usable to un-wedge things in the next few hours. Sorry about this, it's embarrassing this one got through our CI. I personally went all-in on custom images and only did basic sanity testing of local layering, not including across upgrades. We'll get that CI gap covered after this stuff merges because it definitely should work. |
OK, got fresh new builds in the COPR, to apply do e.g.:
That should get things unblocked. But of course, you'll want the fixed version in the new upgrade target too; so there are two ways to do that. One is to stop doing client side layering and add the COPR to a custom container build. The second is to do a persistent local override:
In any case we'll turn the crank and (ideally with confirmation this fixes things for you all) that get a new release out this next week. |
I can confirm the commands and override work for me, I was able to reboot and this new rpm-ostree is functioning normally. Thanks for taking the time on a weekend! 👍🏾 |
I also confirm this fixed my VM install, thank you! |
This closes the CI gap found in fedora-silverblue/issue-tracker#392
(And the CI gap here is plugged by coreos/rpm-ostree#4217 ) |
This fix is now queued in https://bodhi.fedoraproject.org/updates/FEDORA-2022-4ad713eb82 |
Following this workaround helped me get back to a working rpm-ostree. I was using @castrojo ublue-os/base |
Describe the bug
Not sure where to file custom image bugs so let me know if this is the wrong place. I made a custom image and it errors out with this, which I've been able to reproduce on two machines. Seems like it happens a day after I load the image when it's getting an update:
OS version:
Additional context
This breaks the rpm-ostree command, all subcommands appear to be broken now, including rollback.
The text was updated successfully, but these errors were encountered: