tement or add the user locally on the mesos agent
> machines
You can't run as a user that doesn't exist :)
On Wed, Jul 13, 2016 at 7:18 AM, Clarke, Trevor
<tcla...@ball.com<mailto:tcla...@ball.com>> wrote:
I've got an image with a local user and a 'USER myuser' statement in the
Do
I've got an image with a local user and a 'USER myuser' statement in the
Dockerfile. When I try and run a container in mesos (we're using DC/OS but I
think it's mesos related as we're not calling via marathon, etc. it's from a
custom framework) I need "Failed to get user information for
verbose logging with the docker executor
>
>
> > On Mar 17, 2016, at 10:09 AM, Clarke, Trevor <tcla...@ball.com> wrote:
> >
> > Looking in the docker executor, the docker command line is logged with
> VLOG(1) but I'm not sure how to generate that level of log output.
I've got a custom framework running in mesos (0.24.1 for now). It supports
failover and I'd like to be able to start the framework daemons (scheduler,
etc.) from Marathon so I can automatically handle scaling and restart. I'm
running a small cluster where the mesos master is also the primary
I'm currently working on this sort of framework. Unfortunately, source is not
currently available but there is a plan to open source in the next couple of
months. I'm not sure if your need is immediate or if it can wait for a bit. The
framework handles jobs in docker containers with pre and
Take a look at kubernetes.
https://github.com/mesosphere/kubernetes-mesos
From: Pradeep Kiruvale [pradeepkiruv...@gmail.com]
Sent: Monday, October 05, 2015 11:21 AM
To: user; d...@mesos.apache.org
Subject: Scheduling tasks based on dependancy
Hi All,
Are
Is there a way to have mesos combine stderr with stdout in a docker process so
there's only one log stream with proper interleave?
This message and any enclosures are intended only for the addressee. Please
notify the sender by email if you are not the intended recipient. If you are
not
FaQ=jF7FvYH6t0RX1HrEjVCgHQ=BZAdW7eZ7BA-TVm8CsncxQ=myFl_koVz_iyPrvAE5EQBW4Cmn4ocS6C5KCd07WzvjA=PWUrWtXV7HgaC4GxJ0HstRpy_b9dqvCptTljtTzQrx0=>
All of the resource limitations for a docker task should be defined in the
framework.
Thanks,
Guangya
On Wed, Sep 23, 2015 at 9:33 PM, Clarke, Trevor
When a framework accepts an offer and starts a docker task, how does mesos
enforce the task's allocated cpus? Is CPU share used and scaled appropriately?
Are cpu sets explicitly specified to limit execution to the allocated cpus? Is
there a way for a process in the docker container to determine
In the master UI for task status there's an allocated and used value for the
task. Allocated seems to correspond to the amount requested by the scheduler
but I can't seem to figure out how Used is calculated. For mesos command tasks
it doesn't look like it matches virtual or real mem usage in
10 matches
Mail list logo
