mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilbert Song <gilb...@mesosphere.io>
Subject Re: Communicate with a container while using Mesos unified container runtime
Date Fri, 23 Mar 2018 20:47:53 GMT
No, this feature based on Container Attach/Exec
<https://issues.apache.org/jira/browse/MESOS-6460>, which was included
starting from Mesos 1.2.0. I would recommend an upgrade to Mesos 1.4.1 or
1.3.2.

On Thu, Mar 22, 2018 at 5:46 PM, Karan Pradhan <karanpradhan@gmail.com>
wrote:

>
>
> On 2018/03/22 23:16:06, Gilbert Song <gilbert@apache.org> wrote:
> > Hi Karan,
> >
> > It does not seem to me that launching more mesos containers would add
> more
> > overheads.
> >
> > If you want to achieve *docker exec* for debugging purpose, Mesos
> supports
> > that (not in Mesos CLI yet /cc Armand and Kevin), but you could still
> rely
> > on dc/os CLI
> > <https://docs.mesosphere.com/1.11/monitoring/debugging/task-exec/> to do
> > that given you have the taskId.
> >
> > Gilbert
> >
> > On Wed, Mar 21, 2018 at 12:08 PM, Karan Pradhan <karanpradhan@gmail.com>
> > wrote:
> >
> > >
> > >
> > > On 2018/03/21 18:06:48, Gilbert Song <gilbert@apache.org> wrote:
> > > > Hi Karan,
> > > >
> > > > Before figuring out some ways to achieve this with Mesos, I would
> like to
> > > > better understand your use cases.
> > > >
> > > > Do you mean you rely on `docker attach/exec` to send commands to an
> > > > existing running container?
> > > >
> > > > Is there any reason that keeps you from launching a container for
> each
> > > > batch job?
> > > >
> > > > Gilbert
> > > >
> > > > On Wed, Mar 21, 2018 at 10:29 AM, karanpradhan@gmail.com <
> > > > karanpradhan@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I was docker for running my batch job in which I would follow this
> > > > > approach:
> > > > >
> > > > > 1. Start the docker container
> > > > > 2. Send commands to the running Docker container with the help of
> > > docker
> > > > > python client for each batch of objects.
> > > > > 3. After all the batches are processed by the docker, shut down the
> > > > > container.
> > > > >
> > > > > I wanted to achieve the same with the help of Mesos and Marathon
to
> > > spin
> > > > > up containers and submit commands per batch.
> > > > > But looking a the documents it looks like that this behavior is not
> > > > > achievable as when Mesos spin up a Docker container with the help
> of
> > > Mesos
> > > > > containerizer and docker/runtime isolation you can submit only one
> > > command
> > > > > after which the Sesos framework is killed.
> > > > >
> > > > > It would be great if someone could point me to a way to achieve
> this
> > > using
> > > > > Mesos containerizer?
> > > > >
> > > > > Thanks,
> > > > > Karan
> > > > >
> > > >
> > > Hi Gilbert,
> > > Thanks for taking time answering my question.
> > >
> > > Yes as you mentioned I use docker exec to run commands in the
> container.
> > > There is no particular reason why we don't run new docker. Would that
> add
> > > overhead if I had multiple batches which need to be processed?
> > >
> > > Do you know if docker exec is possible on a mesos container running
> with
> > > docker/runtime isolation?
> > >
> > > Thanks,
> > > Karan
> > >
> >
> Thanks Gilbert.
> I have built mesos 1.1.1 from the apache distribution, would dc/os cli
> work for this version too?
>

Mime
View raw message