Kernel: Fix make
#301
Merged
Kernel: Fix make
#301
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Today the kernel subdirectory is somewhat useless. The dockerfile we had tried to use an image that isn't actually on ghcr, so everything would kind of just crap out. This change swaps things so that we build a local image that has all the bits needed to compile the kernel, and then uses that image to build the resulting kernel and plop it in the current working directory. This change does add a reliance on `container` being installed however, but for folks that need to build a custom kernel this doesn't seem like too much of an issue to me.
jglogan
approved these changes
Oct 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #296
Today the kernel subdirectory is somewhat useless. The dockerfile we had tried to use an image that isn't actually on ghcr, so everything would kind of just crap out. This change swaps things so that we build a local image that has all the bits needed to compile the kernel, and then uses that image to build the resulting kernel and plop it in the current working directory. This change does add a reliance on
containerbeing installed however, but for folks that need to build a custom kernel this doesn't seem like too much of an issue to me.