mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marek Zawadzki <mzawad...@mirantis.com>
Subject Re: Official Mesos/Marathon Docker images - please share your thoughts/plans
Date Fri, 08 Jan 2016 08:48:16 GMT
Adam - thank you.
Issue filed (https://github.com/mesosphere/docker-containers/issues/37).

-marek

On 08.01.2016 01:41, Adam Bordelon wrote:
> Officially, Apache prefers to distribute source instead of binaries, which
> is why Mesosphere volunteered to build and distribute rpm/deb packages as
> well as docker images. Apache Mesos could own the Docker files for Mesos
> though.
> That said, if you have problems with the Mesosphere (or mesoscloud) docker
> images for Mesos/Marathon, file an issue with the source repo, and we'd be
> happy to address your issues.
> https://github.com/mesosphere/docker-containers/issues
>
> On Thu, Jan 7, 2016 at 3:00 AM, haosdent <haosdent@gmail.com> wrote:
>
>> hmm, mesoscloud seems not keep updating since 0.24.1
>>
>> On Thu, Jan 7, 2016 at 5:55 PM, Michal Rostecki <mrostecki@mirantis.com>
>> wrote:
>>
>>> On 01/07/2016 10:17 AM, haosdent wrote:
>>>
>>>> Mesoscloud docker file https://github.com/mesoscloud
>>>>
>>>>
>>> Hello haosdent,
>>>
>>> These Dockerfiles don't include the newest versions of
>>>
>>> - Marathon (the newest is 0.13.0, mesoscloud maintains 0.11.0)
>>> - Mesos (the newest is 0.26.0, mesoscloud maintains 0.24.1)
>>>
>>> I recently discovered also a few disadvantages of the mesoscloud images
>>> that are not mentioned in Marek's mail:
>>>
>>> - ZooKeeper is installed from some tarball, while it can be easily
>>> installed from Mesosphere package repository like the other components
>>> - all containers are running as root - there is no need for that except
>>> mesos-slave repo and IMO it's a good practice to run applications as
>>> non-root user if possible
>>>
>>> Cheers,
>>> Michal
>>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>


Mime
View raw message