Bug 2228974

Summary: [RFE] Requesting an osbuild-composer image
Product: Red Hat Enterprise Linux 8 Reporter: jcastran
Component: osbuild-composerAssignee: Image Builder team <osbuilders>
Status: NEW --- QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: high    
Version: 8.8CC: elpereir, obudai, sbarcomb
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jcastran 2023-08-03 19:10:29 UTC
Customers who want to use a container to run osbuild need to follow specific steps such as running the container in privileged mode.

Since this is possible, It would be beneficial if we had a premade image already configured to go.

There are steps here https://github.com/osbuild/osbuild-composer-container#internals for setting up an osbuild container.

Comment 2 Ondřej Budai 2023-08-04 19:30:30 UTC
https://github.com/osbuild/osbuild-composer-container is a purely experimental project for now. Even though we are aware of usecases in which building an image in a privileged container seems to work fine, it's definitely not something that we are currently ready to commit to nor support it.

Specifically for edge images: I believe that RHEL 9 edge images are built with LVM by default. Osbuild currently cannot handle LVM correctly in a container due to inability to configure the host's udev. While you might see an occasional success, there are known race conditions.

I'm afraid that in the current state, we can only improve the documentation that running osbuild in a container is not supported and discouraged. Would it help?