Re: [DISCUSSION] Potential braking change in Mesos 1.6 upgrade - docker thermos based tasks and aurora task ssh

2018-10-22 Thread Renan DelValle
+1 to this idea. It's a good stop gap solution while we explore a better options as well as explore possible corner cases the change to 750 brings. I know that you're busy, so thanks for looking into this as well! -Renan On Mon, Oct 22, 2018 at 9:26 PM Stephan Erb wrote: > Hi Renan, > >

Re: [DISCUSSION] Potential braking change in Mesos 1.6 upgrade - docker thermos based tasks and aurora task ssh

2018-10-22 Thread Stephan Erb
Hi Renan, Unfortunately, it might even be a bit more complicated: The executor is normally launched as root and then drops the privileges for each Thermos process once it got forked successfully. If the Mesos filesystem permissions are too narrow, then subsequent operations managed by those

[DISCUSSION] Potential braking change in Mesos 1.6 upgrade - docker thermos based tasks and aurora task ssh

2018-10-15 Thread Renan DelValle
All, As you may know Mesos has changed the default permissions for the sandbox from 755 (-rwxr-xr-x) to 750 (-rwxr-x---) ( https://issues.apache.org/jira/browse/MESOS-8332). Stephan Erb fixed most of the breakage caused by this change with his recent patch