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
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.
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:
t-lo
changed the title
Propose a mechanism to include sysext builds in the build automation
Propose a mechanism to include sysext builds in the OS image build
Jun 2, 2023
t-lo
changed the title
Propose a mechanism to include sysext builds in the OS image build
Propose a mechanism to enable sysext builds in the OS image build process
Jun 2, 2023
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: