Hi Remy,

Yes with docker bridge network it's not possible yet, with host network it 
should work. I was planning to create a ticket and possibly work on that in the 
future as there are some changes on the spark side.

Tim

> On Nov 4, 2015, at 8:24 AM, PHELIPOT, REMY <remy.pheli...@atos.net> wrote:
> 
> Hello,
>  
> I’m trying to run a spark shell (or a spark notebook) connect to a mesos 
> master inside a docker container. My goal is to give access to the mesos 
> cluster for several user at the same time.
>  
> It seems not possible to get it working with the container started in bridge 
> mode, isn’t it? Is it even possible to run the Spark driver (submit/shell 
> configured in client mode) inside a docker container with Mesos without 
> running it with the –net=host option?
>  
> If my assumptions are verified, it seems not possible to use Spark with 
> docker/Mesos in client mode, right?
>  
> Kind regards,
>  
>  
>  
>  
> Ce message et toutes les pièces jointes (ci-après le "message") sont établis 
> à l’intention exclusive des destinataires désignés. Il contient des 
> informations confidentielles et pouvant être protégé par le secret 
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
> immédiatement l'expéditeur et de détruire le message. Toute utilisation de ce 
> message non conforme à sa destination, toute diffusion ou toute publication, 
> totale ou partielle, est interdite, sauf autorisation expresse de l’émetteur. 
> L'internet ne garantissant pas l'intégrité de ce message lors de son 
> acheminement, Atos (et ses filiales) décline(nt) toute responsabilité au 
> titre de son contenu. Bien que ce message ait fait l’objet d’un traitement 
> anti-virus lors de son envoi, l’émetteur ne peut garantir l’absence totale de 
> logiciels malveillants dans son contenu et ne pourrait être tenu pour 
> responsable des dommages engendrés par la transmission de l’un d’eux.
> 
> This message and any attachments (the "message") are intended solely for the 
> addressee(s). It contains confidential information, that may be privileged. 
> If you receive this message in error, please notify the sender immediately 
> and delete the message. Any use of the message in violation of its purpose, 
> any dissemination or disclosure, either wholly or partially is strictly 
> prohibited, unless it has been explicitly authorized by the sender. As its 
> integrity cannot be secured on the internet, Atos and its subsidiaries 
> decline any liability for the content of this message. Although the sender 
> endeavors to maintain a computer virus-free network, the sender does not 
> warrant that this transmission is virus-free and will not be liable for any 
> damages resulting from any virus transmitted.

Reply via email to