----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44620/#review122997 -----------------------------------------------------------
docs/ssl.md (line 102) <https://reviews.apache.org/r/44620/#comment185118> Not sure exactly how much detail we want to add here about specific configurations (especially considering the upcoming change to the containerizer's environment variables). But here's some more specifics: * When using the DockerContainerizer + normal Mesos agent, the docker executor shares the same root as the agent. So as long as the environment variables are passed on (via the methods you listed), this will work. * When using the DockerContainerizer + dockerized Mesos agent, you will need to add an additional `ContainerInfo.volumes` which mounts from the host (*not the agent*) to the executor. In this case, the task will have access to the keys/certs :( * The UnifiedContainerizer + normal Mesos agent case will probably be similar to the DockerContainerizer + normal Mesos agent case (I haven't tried this). * UnifiedContainerizer + Mesos launched via UnifiedContainerizer ??? - Joseph Wu On March 10, 2016, 5:46 a.m., Jan Schlicht wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/44620/ > ----------------------------------------------------------- > > (Updated March 10, 2016, 5:46 a.m.) > > > Review request for mesos, Adam B and Alexander Rojas. > > > Bugs: MESOS-4750 > https://issues.apache.org/jira/browse/MESOS-4750 > > > Repository: mesos > > > Description > ------- > > see summary > > > Diffs > ----- > > docs/ssl.md 3de2a3e931091e002dc4b259c70eadd89a52b059 > > Diff: https://reviews.apache.org/r/44620/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Jan Schlicht > >
