Does this not satisfy the usecase? ->
https://github.com/ClusterHQ/mesos-module-flocker
On Thu, Nov 26, 2015 at 3:26 AM, Timothy Chen wrote:
> Hi Tommy,
>
> We didn't modify MesosContainerizer container creation but only just
> added image support and the ability to inherit runtime configuration
Hi Tommy,
We didn't modify MesosContainerizer container creation but only just
added image support and the ability to inherit runtime configuration
from images.
We're considering different options like runc for OCI but still just
investigating, if you have any more thoughts let us know!
Tim
On
Tim,
interesting on the MesosContainerizer's design, what technology to support
it? runC solution?
2015-11-25 19:09 GMT+08:00 Timothy Chen :
> Hi there,
>
> DockerContainerizer doesn't support isolators simply because we
> delegate all container creation to Docker via docker client, and
> theref
Hi there,
DockerContainerizer doesn't support isolators simply because we
delegate all container creation to Docker via docker client, and
therefore we don't have a way to run our isolators that's in
mesos-slave from docker.
We're working on unified containerizer that brings Docker images to
Meso
Hi all,
We (Frank Scholten and Phil Winder) are currently developing the Mesos
Flocker framework. As part of this framework we want to develop a
custom isolator module which interacts with the Flocker Control
Service.
After creating a simple stub isolator and installing it on one of the
agents we
