Fedora: Add Support For Applying A Single Patch #36
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.
Adding Support For Applying A Single Patch File (#25)
This pull request addresses #25 modifying the container init process to verify whether a patch file has been mounted to the driver container, and if so to apply it as part of driver compilation. This new mode was used successfully until recently for Fedora40 because prior to the availability of the latest driver containers, e.g. 550.90.07.
The pull request also provides a revised systemd unit snippet for FedoraCoreOS in the
README.md
that attempts to look for a kernel-specific image in a registry, but then falls back to a non-kernel-specific image but seeking to mount any available patches that may allow successful driver compilation.Bumping various dependencies to keep Fedora in sync with
main
Driver, CUDA and Go versions.
FedoraCoreOS GitLab CICD Changes
Various minor changes to the example GitLab CICD scripting.
Addressing Typo As Described in #19