[
https://issues.apache.org/jira/browse/YARN-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595446#comment-16595446
]
Shane Kumpf commented on YARN-8642:
-----------------------------------
Thanks for the patch, [~ccondit-target]! With this patch (+ prior features
we've added), I'm happy to report being able to run systemd as PID 1 in a
non-privileged container!
{quote}In Redhat, tmpfs is automatically created for /run and /run/users/$uid.
How to automate mounting of /run/users/$uid with the current
implementation?{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?
I'm +1 on the latest patch unless there are additional concerns we need to
address.
> 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]
