Personally, I suggest to use the approach @Joseph and @Avinash mentioned. Because zhitao and my patches require Docker >= 1.7.0 .
On Mon, Aug 15, 2016 at 1:27 AM, haosdent <haosd...@gmail.com> wrote: > Not sure if this related to https://issues.apache.org/ > jira/browse/MESOS-2154 > So far we have a quick workaround: specify the `cpu-period` and > `cpu-quota` in the parameters field of `DockerInfo`. Then `Docker::run` > would delegate this to the docker daemon. > > And recently zhitao and me work on the fix for this, we have some under > reviewing patches. I think it should be fixed shortly once zhitao and my > patches ready. > > On Mon, Aug 15, 2016 at 12:11 AM, Erik Weathers <eweath...@groupon.com> > wrote: > >> What was the problem and how did you overcome it? (i.e. This would be a >> sad resolution to this thread for someone faced with this same problem in >> the future.) >> >> >> On Sunday, August 14, 2016, Mark Hammons <mark.hamm...@inaf.cnrs-gif.fr> >> wrote: >> >>> I finally got this working after fiddling with it all night. It works >>> great so far! >>> >>> Mark Edgar Hammons II - Research Engineer at BioEmergences >>> 0603695656 >>> >>> On 14 Aug 2016, at 04:50, Joseph Wu <jos...@mesosphere.io> wrote: >>> >>> If you're not against running Docker containers without the Docker >>> daemon, try using the Unified containerizer. >>> See the latter half of this document: http://mesos.apache.org/docume >>> ntation/latest/mesos-containerizer/ >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__mesos.apache.org_documentation_latest_mesos-2Dcontainerizer_&d=DQMFaQ&c=LNdz7nrxyGFUIUTz2qIULQ&r=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY&m=p3yjpxMelmcew1dQtqJniCFVDpbSbJQBXaW-mA1QVHU&s=6sjCv4C-sSI7jwRLgPi2uCrQR8G0D_Kvtde-tRjBybc&e=> >>> >>> On Sat, Aug 13, 2016 at 7:02 PM, Mark Hammons < >>> mark.hamm...@inaf.cnrs-gif.fr> wrote: >>> >>>> Hi All, >>>> >>>> >>>> >>>> I was having a lot of success having mesos force sandboxed programs to >>>> work within cpu and memory constraints, but when I added docker into the >>>> mix, the cpu limitations go out the window (not sure about the memory >>>> limitations. Is there any way to mix these two methods of isolation? I'd >>>> like my executor/algorithm to run inside a docker container, but have that >>>> container's memory and cpu usage controlled by systemd/mesos. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Mark >>>> -- >>>> >>>> Mark Hammons - +33 06 03 69 56 56 >>>> >>>> Research Engineer @ BioEmergences >>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__bioemergences.iscpif.fr&d=DQMFaQ&c=LNdz7nrxyGFUIUTz2qIULQ&r=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY&m=p3yjpxMelmcew1dQtqJniCFVDpbSbJQBXaW-mA1QVHU&s=hlyM8jpFaEkcQ5X8UJs0BTG53J2X6F-zEs0JIKxCFEQ&e=> >>>> >>>> Lab Phone: 01 69 82 34 19 >>>> >>> >>> > > > -- > Best Regards, > Haosdent Huang > -- Best Regards, Haosdent Huang
