Using alternative managed symbolic links for library paths #4982
Conversation
This file contains 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
…ith 'SymLinks' and 'alternatives'
|
By mistake I squash the commits and some additional conversation can be found here: |
rmccorm4
approved these changes
Oct 14, 2022
This was referenced Nov 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
OBSERVATIONS:
Triton server uses
build.pyto generateDockerfilefor CPU only builds.One of the steps for it is the
COPYlibrary dependencies.As of now those library dependencies are using version specific path instead of using CUDA defined symlinks with alternatives .
HYPOTHESIS
Change hardcoded version values to the defined alternatives.
BENEFITS:
Triton server build became less version agnostic