Fixing AWS env vars #1108
Merged
Fixing AWS env vars #1108
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
|
Hi @fernandomoraes |
|
Thanks @fernandomoraes |
|
Published in v8.6.0 |
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.
Description
Fixing AWS env vars to make work with Layers
Motivation and Context
Without
LD_LIBRARY_PATHcorrect value, layers bin doesn't work correctly. More details about this variables can read hereHow Has This Been Tested?
I found this bug running this layer.
To simulate the problem, create a lambda function with this layer and set this code, when the code is called an error is raised. Entering in docker container, is possible to see that
LD_LIBRARY_PATHdoesn't have/opt/libvalue.After fixing the env value, this layer work as expected.
Screenshots (if appropriate):