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/documentation/latest/mesos-containerizer/
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 <http://bioemergences.iscpif.fr> > > Lab Phone: 01 69 82 34 19 >
