[
https://issues.apache.org/jira/browse/MESOS-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556516#comment-15556516
]
Zameer Manji commented on MESOS-6340:
-------------------------------------
Thermos (Aurora's executor) works around this issue by setting {{$HOME}} to cwd
{{$WORK_DIR}} and/or using {{$MESOS_SANDBOX}} when it is set.
I think [~joshua.cohen] can confirm or deny this.
Personally, if $HOME could default to those values that would be fantastic.
Executors can do their own customization if needed, but setting something would
be better than nothing.
> Set HOME for Mesos tasks
> ------------------------
>
> Key: MESOS-6340
> URL: https://issues.apache.org/jira/browse/MESOS-6340
> Project: Mesos
> Issue Type: Bug
> Components: containerization, slave
> Reporter: Cody Maloney
> Assignee: Jie Yu
>
> Quite a few programs assume {{$HOME}} points to a user-editable data file
> directory.
> One example is PYTHON, which tries to look up $HOME to find user-installed
> pacakges, and if that fails it tries to look up the user in the passwd
> database which often goes badly (The container is running under the `nobody`
> user):
> {code}
> if i == 1:
> if 'HOME' not in os.environ:
> import pwd
> userhome = pwd.getpwuid(os.getuid()).pw_dir
> else:
> userhome = os.environ['HOME']
> {code}
> Just setting HOME by default to WORK_DIR would enable more software to work
> correctly out of the box. Software which needs to specialize / change it (or
> schedulers with specific preferences), should still be able to set it
> arbitrarily and anything a scheduler explicitly sets should overwrite the
> default value of $WORK_DIR
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
