[
https://issues.apache.org/jira/browse/YARN-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596591#comment-16596591
]
Eric Yang commented on YARN-8642:
---------------------------------
{quote}
This need will be dependent on what is running in the container. It would be
nice to be able to reference UID and GID by variable, as you've outlined. Maybe
resolving those variables within the mount related environment variables is a
task the YARN Services AM could handle? Could we discuss in a follow on since
this seems like a useful feature beyond just the tmpfs mounts?{quote}
I was thinking to partition it via container id or some mechanism that can be
clean up automatically. YARN service or upper layer don't have the visibility
to absolute path or convention used in container-executor. It might be better
to keep this path logic contained in DockerLinuxContainerRuntime. Sorry, I
replied too late, will open another JIRA to refine this.
> Add support for tmpfs mounts with the Docker runtime
> ----------------------------------------------------
>
> Key: YARN-8642
> URL: https://issues.apache.org/jira/browse/YARN-8642
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Shane Kumpf
> Assignee: Craig Condit
> Priority: Major
> Labels: Docker
> Fix For: 3.2.0, 3.1.2
>
> Attachments: YARN-8642.001.patch, YARN-8642.002.patch
>
>
> Add support to the existing Docker runtime to allow the user to request tmpfs
> mounts for their containers. For example:
> {code}/usr/bin/docker run --name=container_name --tmpfs /run image
> /bootstrap/start-systemd
> {code}
> One use case is to allow systemd to run as PID 1 in a non-privileged
> container, /run is expected to be a tmpfs mount in the container for that to
> work.
--
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
