Update Dockerfile for nvidia runtime #1585
Open
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
|
@all-contributors please add @nlosg for code and ideas and doc. |
|
I've put up a pull request to add @nlosg! 🎉 |
Setting the runtime to default to nvidia as these are GPU nodes and will likely run GPU-accelerated workloads only. I'm happy to have this optional to avoid confusion but I think it's beneficial to include it for those wondering.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Setting the runtime to default to nvidia as these are GPU nodes and will likely run GPU-accelerated workloads only. I'm happy to have this as optional to avoid confusion but I think it's beneficial for users to decide for themselves how to manage the configuration.
What
Creates a K3s configuration file setting the default runtime to nvidia. This configuration is passed at cluster bringup when k3s agent is run.
Why
I don't see any issue for GPU specific nodes and it avoids the overhead of defining the runtime in every YAML definition.
Implications
N/A