Allow LD_LIBRARY_PATH read from config #1408
Merged
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
eyberg
approved these changes
Jan 17, 2023
Contributor
Author
|
@eyberg, would it be possible we get a new release at this point? |
Contributor
|
yeh it's been a while - went ahead and cut a new version |
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.
Currently we support reading LD_LIBRARY_PATH from host and from ELF section. This PR adds third option to read from config to improve the command-line experience.
# before $ LD_LIBRARY_PATH=/tmp/linux/lib:/tmp/linux/usr/lib:/tmp/linux/lib/x86_64-linux-gnu:/tmp/linux/usr/lib/x86_64-linux-gnu \ ops run -c config.json publish/myApp