[jira] [Commented] (MESOS-4750) Mesos Executor expects all SSL_* environment variables to be set

["Adam B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15160294#comment-15160294 ] 

Adam B commented on MESOS-4750:
-------------------------------

cc: [~jvanremoortere], [~kaysoky]

> Mesos Executor expects all SSL_* environment variables to be set
> ----------------------------------------------------------------
>
>                 Key: MESOS-4750
>                 URL: https://issues.apache.org/jira/browse/MESOS-4750
>             Project: Mesos
>          Issue Type: Documentation
>          Components: documentation, general, slave
>    Affects Versions: 0.26.0
>            Reporter: pawan
>              Labels: documentation, mesosphere, ssl
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> I was trying to run Docker containers in a fully SSL-ized Mesos cluster but ran into problems because the executor was failing with a "Failed to shutdown socket with fd 10: Transport endpoint is not connected".
> My understanding of why this is happening is because the executor was trying to report its status to Mesos slave over HTTPS, but doesnt have the appropriate certs/env setup inside the executor.
> (Thanks to mslackbot/joseph for helping me figure this out on #mesos)
> It turns out, the executor expects all SSL_* variables to be set inside `CommandInfo.environment` which gets picked up by the executor to successfully reports its status to the slave.
> This part of __executor needing all the SSL_* variables to be set in its environment__ is missing in the Mesos SSL transitioning guide. I request you to please add this vital information to the doc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)