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
Many interesting Kernel modules and not always available as loadable modules and/or the default enabled modules are not always matching your specifics needs/regulatory requirements.
The current Mariner build system already support generating Mariner images and packages.
The goal of this ticket is to implement a third mode to generate Mariner's kernel with default or custom Kconfig
It could be delivery/maintained as a container image for (re)building the kernel for both WSL and Mariner (see #3549)
The text was updated successfully, but these errors were encountered:
Hello @eric-desrochers, at the latest Microsoft Ignite conference last week, you will hear that Microsoft's top executives (like @scottgu) confirmed the strategic goal of supporting "all enterprise workloads." My original post above just provides one of the key requirement to achieve this goal.
Many interesting Kernel modules and not always available as loadable modules and/or the default enabled modules are not always matching your specifics needs/regulatory requirements.
The current Mariner build system already support generating Mariner images and packages.
The goal of this ticket is to implement a third mode to generate Mariner's kernel with default or custom Kconfig
It could be delivery/maintained as a container image for (re)building the kernel for both WSL and Mariner (see #3549)
The text was updated successfully, but these errors were encountered: