Thanks Cody, exactly the info I was looking for. Do you know which volumes need mounting? Just the mesos data directories, or additional system directories also?
On Tue, Dec 2, 2014 at 3:02 PM, Cody Maloney <[email protected]> wrote: > Mesos inside docker definitely can work. There are some issues with the > slave in some cases (You can't have any containers which start with > 'mesos-' on the slave, don't put two slaves on the same host. > https://issues.apache.org/jira/browse/MESOS-2016 is one of the issues > which you'll likely run into. > > If slave recovery is important (Being able to upgrade the mesos-slave > binary without killing all the running tasks), then be sure to test that. > It's really easy for it not to work when inside docker. There are a number > of flags you need to pass to docker to make everything work right > (privileged, net=host, volume mount a couple directories so they persist > docker container restart among others). > > On Tue, Dec 2, 2014 at 10:07 AM, George Blazer <[email protected]> wrote: > >> We are running Mesos inside of Docker. >> >> It didn't make it into production yet, but I'm not seeing any issues at >> this point. >> >> On Tue, Dec 2, 2014 at 10:01 AM, Steven Schlansker < >> [email protected]> wrote: >> >>> >>> On Dec 2, 2014, at 8:22 AM, Jeremy Jongsma <[email protected]> wrote: >>> >>> > What is the current state of running Mesos inside Docker? I ran across >>> a thread that indicates it may be working now, but I have not seen any >>> Docker images for Mesos from authoritative sources. >>> > >>> > https://www.mail-archive.com/[email protected]/msg01616.html >>> > >>> > Is anybody doing this in production? Are there known issues? >>> > >>> > We already have a base AMI for deploying and updating Docker >>> containers across our infrastructure, so adding Mesos inside that would be >>> a simple way to start using it. >>> >>> I'm also interested in this, and can help contribute to an existing >>> Mesos packaging if we find one or can collaborate on creating one if >>> there's no suitable project already. >>> >>> >>> >> >
