You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there's some back-and-forth and shared code between bootupd and bootc here. It seems the fix was added in bootc 1.15.2 but bootupd requires bootc-internal-blockdev = "1.15.1"; perhaps we need an updated bootupd? A dependabot PR for that is open: coreos/bootupd#1102
I have the following setup of devices and partitions mounted to /run/osbuild/mounts. When calling bootc install to-filesystem ... /run/osbuild/mounts it errors out unable to find the PReP partition. I think the following PRs and issues are related:
Here is some additional information of what I see; all of these commands are executed inside the bubblewrap sandbox that osbuild runs bootc in. We are running bootc 1.15.2.
This was reported to us by the COPR folks through: osbuild/bootc-image-builder#1223 and I've asked the CoreOS folks to confirm and they see the same issue.
bootc has definitely found the appropriate loopback device and the loopback device seems to contain all the necessary information.
I think there's some back-and-forth and shared code between
bootupdandbootchere. It seems the fix was added inbootc1.15.2 butbootupdrequiresbootc-internal-blockdev = "1.15.1"; perhaps we need an updatedbootupd? A dependabot PR for that is open: coreos/bootupd#1102I have the following setup of devices and partitions mounted to
/run/osbuild/mounts. When callingbootc install to-filesystem ... /run/osbuild/mountsit errors out unable to find the PReP partition. I think the following PRs and issues are related:osbuildwhich was determined to not be a good idea.bootc.Here is some additional information of what I see; all of these commands are executed inside the
bubblewrapsandbox thatosbuildrunsbootcin. We are runningbootc1.15.2.This was reported to us by the COPR folks through: osbuild/bootc-image-builder#1223 and I've asked the CoreOS folks to confirm and they see the same issue.
bootchas definitely found the appropriate loopback device and the loopback device seems to contain all the necessary information.The exact call I think
bootc1.15.2 is using to find things returns the correct GUID.When calling
bootc install to-filesystem ...I get the following error:Additional (potentially not very useful) bits: