[
https://issues.apache.org/jira/browse/MESOS-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961314#comment-14961314
]
Jay Taylor commented on MESOS-3712:
-----------------------------------
This ticket should be merged into
https://issues.apache.org/jira/browse/MESOS-3738. I've tested the patch in
3738 and it fixed all broken aspects of health-check invocation.
> --launcher_dir flag is not picked up when running health-checks
> ---------------------------------------------------------------
>
> Key: MESOS-3712
> URL: https://issues.apache.org/jira/browse/MESOS-3712
> Project: Mesos
> Issue Type: Bug
> Components: slave
> Affects Versions: 0.24.1, 0.25.0
> Environment: Ubuntu Linux x64
> Reporter: Jay Taylor
> Labels: containerizer, mesosphere, tech-debt
>
> Mesos configuration flags are one-way and aren't expanded to their
> corresponding MESOS_ENV variable.
> The {{MESOS_LAUNCHER_DIR}} however, is necessary [here|
> https://github.com/apache/mesos/blob/master/src/docker/executor.cpp#L573-L576]:
> {code}
> const Option<string> envPath = os::getenv("MESOS_LAUNCHER_DIR");
> string path =
> envPath.isSome() ? envPath.get()
> : os::realpath(Path(argv[0]).dirname()).get();
> {code}
> when the executor needs to resolve the path to run, for example,
> health-checks.
> Instead of the passed-in argument {{argv[0]}} (which contains the Agent's
> {{--work_dir}} instead) is the path that ends up being used.
> How can the requisite MESOS_LAUNCHER_DIR env var be available when
> {{docker/executor.cpp}} (a child process of {{mesos-slave}}) attempts to read
> it?
> ----
> The relevant email thread is here:
> http://www.mail-archive.com/[email protected]/msg04794.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
