-
Notifications
You must be signed in to change notification settings - Fork 31
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
Propose a mechanism to enable sysext builds in the OS image build process #1052
Comments
@krishjainx wanted to look into this. |
I think we can already close this since it's merged? @t-lo |
Not until the build process produces docker/containerd sysexts that work. |
Good point, @jepio . |
The script is now used for both the OEMs as well as the inbuilt Docker+containerd sysext images. |
The OS image we currently produce is unsuitable as a base for building Flatcar specific sysext images: it lacks package information and portage configuration. During the image build process our low-level build automation removes this information from the OS image to keep it lean.
In order to build sysext images suitable for running on a specific OS release, the image build needs to be extended to produce artifacts retaining this information.
Part of the work is already in progress here: flatcar/scripts#858
This issue builds on that work with the aim to make it more generally usable for all future Flatcar / version specific sysext builds.
The text was updated successfully, but these errors were encountered: