[
https://issues.apache.org/jira/browse/YARN-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595336#comment-16595336
]
Craig Condit commented on YARN-8642:
------------------------------------
[~ebadger], the regex is based on the one used for normal mounts. The
container-executor process never uses these values in a shell context, but
simply adds the entire value as an argument to exec(), which in turn is passed
as the argument following {{--tmpfs}} in docker. I have verified that passing
in things such as your example results in the mountpoint being literally named:
{noformat}
. /foo/bar || <execute_bad_code>
{noformat}
This is expected.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
