Bingo. It probably doesn't hurt to differentiate --runtime_dir per agent but the real problem is that --cgroups_root needs to be different too. As one might infer from linux_launcher.cpp:
Future<hashset<ContainerID>> LinuxLauncherProcess::recover( > const list<ContainerState>& states) > { > // Recover all of the "containers" we know about based on the > // existing cgroups. > Try<vector<string>> cgroups = > cgroups::get(freezerHierarchy, flags.cgroups_root); Thanks much. On Wed, Nov 15, 2017 at 11:37 AM, James Peach <jor...@gmail.com> wrote: > > > On Nov 15, 2017, at 8:24 AM, Dan Leary <d...@touchplan.io> wrote: > > > > Yes, as I said at the outset, the agents are on the same host, with > different ip's and hostname's and work_dir's. > > If having separate work_dirs is not sufficient to keep containers > separated by agent, what additionally is required? > > You might also need to specify other separate agent directories, like > --runtime_dir, --docker_volume_checkpoint_dir, etc. Check the output of > mesos-agent --flags. > > > > > > > On Wed, Nov 15, 2017 at 11:13 AM, Vinod Kone <vinodk...@apache.org> > wrote: > > How is agent2 able to see agent1's containers? Are they running on the > same box!? Are they somehow sharing the filesystem? If yes, that's not > supported. > > > >