[
https://issues.apache.org/jira/browse/YARN-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814694#comment-16814694
]
caozhiqiang commented on YARN-9379:
-----------------------------------
I have add yarn.nodemanager.runtime.linux.docker.allowed-container-runtimes
property in yarn-site.xml config to fail fast. But I don't add a
"default-container-runtime" in yarn-site.xml. The reason is that: firstly,
without --runtime parameter, docker will run with runc runtime to run a
container; secondly, if add a "default-container-runtime", it will always pass
a runtime parameter to container-executor, and the docker.allowed.runtimes
property will must be set in container-executor.cfg. Or the task using docker
will fail for container-executor not allowed.
> Can't specify docker runtime through environment
> ------------------------------------------------
>
> Key: YARN-9379
> URL: https://issues.apache.org/jira/browse/YARN-9379
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.3.0
> Reporter: caozhiqiang
> Assignee: caozhiqiang
> Priority: Minor
> Attachments: YARN-9379-branch-3.2.0.001.patch, YARN-9379.002.patch,
> YARN-9379.003.patch, YARN-9379.004.patch, YARN-9379.005.patch
>
>
> When use docker to run yarn containers, even though there is
> docker.allowed.runtimes in container-executor.cfg, there are not parameter to
> specify the docker runtime, such as gvisor, lxc or kata. With this patch,
> client can add parameter such as
> -[Dyarn.app.mapreduce.am|http://dyarn.app.mapreduce.am/].env.YARN_CONTAINER_RUNTIME_DOCKER_RUNTIME=runsc
> to specify docker runtime.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
