Hello all.
This is Marek Zawadzki from Mirantis Kolla Team - I've met Brenden
Matthews & Ben Lin at Mesosphere SF office this October.
We work on deploying OpenStack on Mesos/Marathon cluster using Kolla
<https://wiki.openstack.org/wiki/Kolla> and we find Docker a great way
for quickly setting up our environment.
Could you please share your thoughts about Docker images for Mesos/Marathon?
TL; DR: the images that can be found on DockerHub are either out of date
or not working. We would like to know your plans about maintaining them.
You can find details in Michal Rostecki's (Kolla core reviewer) email below.
Thanks!
-marek
--
Marek Zawadzki
Mirantis Kolla Team
-------- Forwarded Message --------
Subject: Mesosphere Docker images
Date: Wed, 23 Dec 2015 14:11:40 +0100
From: Michal Rostecki <[email protected]>
[...]
I recently found the official Docker images from Mesosphere:
https://hub.docker.com/u/mesosphere/
https://github.com/mesosphere/docker-containers
In theory, we should be able to set up a Mesos cluster using these
images. In practice, I ran into the following problems:
1. ZooKeeper -https://hub.docker.com/r/mesosphere/zookeeper/
First of all - I don't see any source code of this image. Dockerfile for
it just doesn't exists om their Github (mesosphere/docker-containers).
To figure out how their start script works, I had to access the file
inside the container and search for it.
Second thing - it binds to the localhost address, instead of 0.0.0.0 or
concrete IP address. I didn't see any option in their start scripts to
configure that. That makes multinode installation impossible, but it
even makes working on all-in-one hard too - because a good practice is
to point Mesos master and Marathon to the public IP of ZooKeeper, even
if all of these services are running on the same node.
2. Mesos slave -https://hub.docker.com/r/mesosphere/mesos-slave/
It doesn't have Docker installed. The comments on dockerhub confirm
this. It makes using docker containerized impossible. This image works
only with cgroups containerized, so it's useless for us.
3. Chronos -https://hub.docker.com/r/mesosphere/chronos/
It requires configuring via volume containing config file. It's in
contradiction with the other images which are configured via env
variables. We would like to configure all Mesos stuff via env.
That's all about Mesosphere's images.
In kolla-mesos, we're currently using images from
https://hub.docker.com/r/mesoscloud/ - this account doesn't seem to be
associated with any company.
Images from mesoscloud work perfectly, but are outdated - especially
about Marathon which is released often.
On the other hand, mesosphere images have the newest versions, are last
built no earlier than a week ago, but well, they just don't work good
for us.
That's why we would like Mesosphere to improve quality of their images.
This may block our work.
Regards,
Michal
