Re: Mesos loses track of Docker containers

Thank you, Sivaram. That would seem to be 2 "votes" for upgrading. -Paul > On Aug 13, 2016, at 11:47 PM, Sivaram Kannan wrote: > > > I don't remember the condition exactly, but I have faced similar issue in my > deployments and have been fixed when I moved to 0.26.0.

Re: Mesos loses track of Docker containers

I don't remember the condition exactly, but I have faced similar issue in my deployments and have been fixed when I moved to 0.26.0. Upgrade the marathon to compatible version as well. On Wed, Aug 10, 2016 at 9:30 AM, Paul Bell wrote: > Hi Jeff, > > Thanks for your reply. >

Re: Mesos loses track of Docker containers

Hi Jeff, Thanks for your reply. Yeahthat thought occurred to me late last night. But customer is sensitive to too much churn, so it wouldn't be my first choice. If I knew with certainty that such a problem existed in the versions they are running AND that more recent versions fixed it, then

Re: Mesos loses track of Docker containers

Have you considered upgrading Mesos and Marathon? Those are quite old versions of both with some fairly glaring problems with the docker containerizer if memory serves. Also what version of docker? On Wednesday, August 10, 2016, Paul Bell wrote: > Hello, > > One of our

Mesos loses track of Docker containers

Hello, One of our customers has twice encountered a problem wherein Mesos & Marathon appear to lose track of the application containers that they started. Platform & version info: Ubuntu 14.04 (running under VMware) Mesos (master & agent): 0.23.0 ZK: 3.4.5--1 Marathon: 0.10.0 The phenomena: