[
https://issues.apache.org/jira/browse/MESOS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482142#comment-14482142
]
Niklas Quarfot Nielsen commented on MESOS-2592:
-----------------------------------------------
Like the command.user tests (which I had to disable due to too limited
privileges for `nobody`), there were no tests that verified the ownership as
our tests haven't made any assumptions around a test or 'mesos' user. Think it
would be generally useful to have a well-known (or configurable) user for
mesos, so we can test these scenarios.
> The sandbox directory is not chown'ed if the fetcher doesn't run
> ----------------------------------------------------------------
>
> Key: MESOS-2592
> URL: https://issues.apache.org/jira/browse/MESOS-2592
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.22.0
> Reporter: Niklas Quarfot Nielsen
> Priority: Blocker
> Attachments: switchUser.patch
>
>
> We have run into issues with the sandbox permissions and ownership. It looks
> like the sandbox isn't chown'ed if no URIs are put in the task info. Recent
> changes have moved the chown'ing from the containerizer to the fetcher,
> however if the fetcher isn't run - the sandbox owner will remain the user of
> the slave (in our case, root).
> Have anyone run into something similar?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
