[
https://issues.apache.org/jira/browse/YARN-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259990#comment-16259990
]
Shane Kumpf commented on YARN-5534:
-----------------------------------
I've updated the title and description to better reflect the current scope of
the issue. I'm attaching a new patch that adds support for the user provided
mount list.
One item I did want to discuss. We do still have
{{YARN_CONTAINER_RUNTIME_DOCKER_LOCAL_RESOURCE_MOUNTS}} which I believe we
could do away with in favor of {{YARN_CONTAINER_RUNTIME_DOCKER_MOUNTS}}. The
challenge is the additional validation currently being done for that option and
it would be a change in behavior. I don't think the additional validation is
necessary with the changes in YARN-6623, and any validation should be handled
by c-e anyway. I don't expect
{{YARN_CONTAINER_RUNTIME_DOCKER_LOCAL_RESOURCE_MOUNTS}} has been widely used
outside of yarn native services, but I don't know for certain. /cc
[~billie.rinaldi]
> Allow user provided Docker volume mount list
> --------------------------------------------
>
> Key: YARN-5534
> URL: https://issues.apache.org/jira/browse/YARN-5534
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: luhuichun
> Assignee: Shane Kumpf
> Attachments: YARN-5534.001.patch, YARN-5534.002.patch,
> YARN-5534.003.patch
>
>
> YARN-6623 added support in container-executor for admin supplied Docker
> volume whitelists. This allows controlling which host directories can be
> mounted into Docker containers launched by YARN. A read-only and read-write
> whitelist was added. We now need the ability for users to supply the mounts
> they require for their application, which will be validated against the admin
> whitelist in container-executor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
