[
https://issues.apache.org/jira/browse/YARN-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424717#comment-16424717
]
Eric Yang commented on YARN-8097:
---------------------------------
For preventing filename clashing, it would be useful to ask user for the
filename that contains environment variables. From YARN service, the
submission file looks like this:
{code}
{
"name": "hive-service",
"kerberos_principal" : {
"principal_name" : "hive/[email protected]",
"keytab" : "file:///etc/security/keytabs/hive.service.keytab"
},
"version": "1",
"components" :
[
{
"name": "hiveserver2",
"number_of_containers": 2,
"artifact": {
"id": "hadoop/centos:latest",
"type": "DOCKER"
},
"files": [
{
"type": "STATIC",
"dest_file": "production.env",
"src_file": "hdfs:///app/hive/env/production.env"
}
],
"env-file": "production.env",
"resource": {
"cpus": 1,
"memory": "256"
},
"configuration": {
"env": {
"YARN_CONTAINER_RUNTIME_DOCKER_DELAYED_REMOVAL":"true"
},
"properties": {
"docker.network": "host"
}
}
}
]
}
{code}
This approach can avoid internally generated filename by node manager clash
with user supplied configuration filename in the localized directory.
> Add support for Docker env-file switch
> --------------------------------------
>
> Key: YARN-8097
> URL: https://issues.apache.org/jira/browse/YARN-8097
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Affects Versions: 3.2.0
> Reporter: Eric Yang
> Priority: Major
>
> There are two different ways to pass user environment variables to docker.
> There is -e flag and --env-file which reference to a file that contains
> environment variables key/value pair. It would be nice to have a way to
> express env-file from HDFS, and localize the .env file in container localized
> directory and pass --env-file flag to docker run command. This approach
> would prevent ENV based password to show up in log file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
