[
https://issues.apache.org/jira/browse/YARN-9959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974452#comment-16974452
]
Eric Badger commented on YARN-9959:
-----------------------------------
[[email protected]] pointed out in our latest docker meeting that there is
a correctness issue with having these hard-coded mounts. If anyone mounts onto
/tmp or /var/tmp in their container then they will get a circular mount that
can't be cleaned up and is overall pretty gross. You can see the logs of this
in [this
comment|https://issues.apache.org/jira/browse/YARN-9562?focusedCommentId=16971141&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16971141].
For now, I have added a documentation comment noting that mounting on top of
/tmp or /var/tmp is not supported. However, this is a limitation that we should
not need to have.
> Work around hard-coded tmp and /var/tmp bind-mounts in the container's
> working directory
> ----------------------------------------------------------------------------------------
>
> Key: YARN-9959
> URL: https://issues.apache.org/jira/browse/YARN-9959
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Badger
> Priority: Major
>
> {noformat}
> addRuncMountLocation(mounts, containerWorkDir.toString() +
> "/private_slash_tmp", "/tmp", true, true);
> addRuncMountLocation(mounts, containerWorkDir.toString() +
> "/private_var_slash_tmp", "/var/tmp", true, true);
> {noformat}
> It would be good to remove the hard-coded tmp mounts from the
> {{RuncContainerRuntime}} in place of something general or possibly a tmpfs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
