[
https://issues.apache.org/jira/browse/MESOS-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629784#comment-16629784
]
Till Toenshoff commented on MESOS-6340:
---------------------------------------
I ran into this challenge (trap?!) myself. The symptom was curl failing to work
as soon as SSL certificate validation was enabled with a rather nonsensical
"curl: (27) Out of memory}}. This happens due to curl failing to gain knowledge
of the home-dir of the user in my docker image.
Let's please improve this soon and / or document all the possible shortcomings,
sparing our users the debug sessions.
> Set HOME for Mesos tasks
> ------------------------
>
> Key: MESOS-6340
> URL: https://issues.apache.org/jira/browse/MESOS-6340
> Project: Mesos
> Issue Type: Bug
> Components: agent, containerization
> Reporter: Cody Maloney
> Priority: Major
> Labels: containerizer
>
> 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
(v7.6.3#76005)
