On Sun, Feb 11, 2018 at 6:00 PM James Peach wrote:
>
>
> > On Feb 9, 2018, at 9:28 PM, Michael Park wrote:
> >
> > I'm going to put this up for a vote. My plan is to bump us to C++14 on
> Feb
> > 21.
> >
> > The following are the proposed changes:
> > - Minimum GCC *4.8.1* => *5*.
> > - Minimu
mini-mesos being so far behind is too bad. If it had a more modern version
of Mesos working it would be useful. It's killer features as far as I'm
concerned are the inclusion of mesos-dns and Marathon in that order.
Having mesos-dns in this docker image would be valuable.
On Sun, Feb 11, 2018 at
> On Feb 9, 2018, at 9:28 PM, Michael Park wrote:
>
> I'm going to put this up for a vote. My plan is to bump us to C++14 on Feb
> 21.
>
> The following are the proposed changes:
> - Minimum GCC *4.8.1* => *5*.
> - Minimum Clang *3.5* => *3.6*.
> - Minimum Apple Clang *8* => *9*.
>
> We'll
Thanks for the pointer. Yes, I am aware of https://www.minimesos.org, which
uses a vagrant like workflow (the last release was 11 months ago).
My goal is to have a single docker image that contains all the components,
so that running the entire stack will be just a single `docker run`.
Another goa
Hi,
When we were developing a framework with Mesos, we realized that it'll be
great to have a Docker image that allows framework developers to quickly
test with Mesos APIs (preferably new APIs that haven't been released yet).
The docker container will have both Mesos master and agent running,
allo