Mailing-List: contact user-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@mesos.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for user@mesos.apache.org)
MIME-Version: 1.0
Date: Mon, 4 May 2015 15:58:57 -0700
Message-ID: 
 <CAFwM5HyuDyH2LrKr=8O60YJ0RV1SOP23U7+zc4z-WbzQRU-eRg@mail.gmail.com>
Subject: bridging a mesos-launched container to public (local) network
From: No One <jc.listmail@gmail.com>
To: user@mesos.apache.org
Content-Type: multipart/alternative; boundary=001a11c3e104c1405605154981e4

--001a11c3e104c1405605154981e4
Content-Type: text/plain; charset=UTF-8

I have a specific Docker container use case, that requires the container to
get a DHCP address from my local network.  I've been accomplishing this
using networking containers that use Pipework to bridge to the host
interface and link to the app container (
https://github.com/jeroenpeeters/docker-network-containers).

I'm trying to figure out how to accomplish the same thing within the
Mesos/Marathon framework - how can I launch a container can be bridged onto
my local network so that it can receive (and run) an IP via DHCP?

I could potentially just continue using docker-network-containers, but I
need some way to make sure the network container lands on the same slave as
the app container.  Or, I need to figure out some other method of getting a
particular container on my local network altogether.

Thanks!
Jay

--001a11c3e104c1405605154981e4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have a specific Docker container use case, that requires=
 the container to get a DHCP address from my local network.=C2=A0 I&#39;ve =
been accomplishing this using networking containers that use Pipework to br=
idge to the host interface and link to the app container (<a href=3D"https:=
//github.com/jeroenpeeters/docker-network-containers">https://github.com/je=
roenpeeters/docker-network-containers</a>).<div><br></div><div>I&#39;m tryi=
ng to figure out how to accomplish the same thing within the Mesos/Marathon=
 framework - how can I launch a container can be bridged onto my local netw=
ork so that it can receive (and run) an IP via DHCP?</div><div><br></div><d=
iv>I could potentially just continue using docker-network-containers, but I=
 need some way to make sure the network container lands on the same slave a=
s the app container.=C2=A0 Or, I need to figure out some other method of ge=
tting a particular container on my local network altogether.</div><div><br>=
</div><div>Thanks!</div><div>Jay</div></div>

--001a11c3e104c1405605154981e4--