[
https://issues.apache.org/jira/browse/YARN-9053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702066#comment-16702066
]
Charo Zhang commented on YARN-9053:
-----------------------------------
[~Jim_Brennan] [~eyang] it's true that variables are defined in
launch_script.sh, but it's only valid for launch_script.sh. Docker environment
should be global valid （it's existed in "env" command output）.
The environment variables pass to container by set_env method in docker-util.c,
which will reading a env file. And the env file records all environment
variables added by "addEnv" in DockerRunCommand.java. All values in env file
are global valid after passed in Docker Container.
> Support set environment variables for Docker Containers In nonEntryPoint mode
> -----------------------------------------------------------------------------
>
> Key: YARN-9053
> URL: https://issues.apache.org/jira/browse/YARN-9053
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: nodemanager
> Affects Versions: 3.1.1
> Reporter: Charo Zhang
> Priority: Major
> Labels: Docker
> Attachments: YARN-9053.patch
>
>
> In yarn 3.1.1, users can only set environment variables with "-shell_env" in
> ENTRYPOINT mode, and variables must be registered in
> yarn.nodemanager.env-whitelist.
> But in nonEntryPoint mode, we should allow users to set environment variables
> like "-e KEY=VAULE" in docker run command, too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
