We considered support --user option in docker containerizer. Unfortunately, it would potentially break some previous users in behavior. So we did not merge it. Please see this JIRA for detail:
https://issues.apache.org/jira/browse/MESOS-5754 However, you can still use DockerInfo::Parameter to specify your --user as a workaround. Gilbert On Thu, Sep 1, 2016 at 9:15 AM, Olivier Sallou <[email protected]> wrote: > > > ----- Mail original ----- > > De: "Qian Zhang" <[email protected]> > > À: [email protected] > > Envoyé: Jeudi 1 Septembre 2016 15:57:39 > > Objet: Re: Docker containerizer: override USER > > > > Hi Olivier, > > > > Can you try TaskInfo.CommandInfo.user? > > I will try but mesos.proto specifies: > > // Enables executor and tasks to run as a specific user. If the user > // field is present both in FrameworkInfo and here, the CommandInfo > // user value takes precedence. > > FrameworkInfo.user is specified in my case and set to the expected user > XX. So it does not seem that the container is executed wit the --user XX > flag. > > Olivier > > > > > > > > Thanks, > > Qian Zhang > > > > On Thu, Sep 1, 2016 at 4:39 PM, Olivier Sallou <[email protected]> > > wrote: > > > > > Hi, > > > If Docker image specified a USER in Dockerfile, docker will use this > user > > > when executing command in container. > > > In Docker commands, it can be overriden with -u XX . > > > > > > I do not find however in mesos.proto a way to do so. There is the > > > "arguments" of DockerInfo that I could use to append this to the > executor > > > command line, but I think it is not advised as it may not be supported > in > > > future. > > > > > > Did I miss something ? > > > > > > Thanks > > > > > > Olvier > > > > > >
