[
https://issues.apache.org/jira/browse/MESOS-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378313#comment-15378313
]
Jie Yu edited comment on MESOS-5754 at 7/15/16 4:33 PM:
--------------------------------------------------------
Some notes here:
This change will potentially break some of the existing Mesos users. For
instance, if their running cluster has `--switch-user` being turned on, here is
the difference:
Before: the docker container will run under uid=0 (assuming image does not
specify a user), it's able to create directories under /var/lib
After: the docker container will run under the user specified in commandInfo or
frameworkInfo. It might not be able to write to directories like /var/lib
was (Author: jieyu):
Some notes here:
This change will potentially break some of exiting Mesos users. For instance,
if their running cluster has `--switch-user` being turned on, here is the
difference:
Before: the docker container will run under uid=0 (assuming image does not
specify a user), it's able to create directories under /var/lib
After: the docker container will run under the user specified in commandInfo or
frameworkInfo. It might not be able to write to directories like /var/lib
> CommandInfo.user not honored in docker containerizer
> ----------------------------------------------------
>
> Key: MESOS-5754
> URL: https://issues.apache.org/jira/browse/MESOS-5754
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker, slave
> Affects Versions: 1.0.0
> Reporter: Michael Gummelt
> Assignee: Gilbert Song
> Labels: mesosphere
>
> Repro by creating a framework that starts a task with CommandInfo.user set,
> and observe that the dockerized executor is still running as the default
> (e.g. root).
> cc [~kaysoky]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
