-
Notifications
You must be signed in to change notification settings - Fork 198
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
COSA container failing to build using OSBuild #5251
Comments
This relates to containers/bootc#915 likely |
|
And um...this is running osbuild inside supermin right? |
Yes |
OK right we merged #5227 which was written assuming that the invoking process was bootc but here it's rpm-ostree |
This is aiming to fix coreos/rpm-ostree#5251 Basically we can't re-invoke the calling process if we aren't actually bootc. (There are solutions that make this work, but what we'll hopefully do shortly is propagate the logic to older streams to have bootc take over the handling anyways) Signed-off-by: Colin Walters <walters@verbum.org>
OK us vendoring a bootc with containers/bootc#1059 should fix this, testing |
The other fix would be to push through https://github.com/containers/bootc/blob/6ff180b56a2ff430ee4ac94c9a089a936fec3f4e/contrib/packaging/bootc.spec#L2 to f41, but eh |
The FCOS CI on rpm-ostree should have caught this as far as I know...I don't understand how it didn't. We're deploying the new rpm-ostree on top of existing coreos-assembler which should be this same scenario. |
Yeah. I was wondering about this too. |
I would have sworn we were doing this before, but if so I can't find it in git logs. We want to test the new rpm-ostree at build time too of course. xref coreos#5251 (comment)
okay now I'm getting
Okay guess I need to nuke |
And to be clear this should all work in rawhide/c10s where bootc owns Anyways I can confirm containers/bootc#1059 fixes this. |
https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/blue/organizations/jenkins/build/detail/build/3319/pipeline/
The OSBuild stage is failing during the
ostree container image deploy
step:As of recently the
ostree container
command redirects to bootc. Could we somehow not have bootc or a tool old bootc in this image?The text was updated successfully, but these errors were encountered: