Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
To our knowledge, no one is using the external containerizer and we could clean up code paths in the slave and containerizer interface (the dual launch() signatures)
In a deprecation cycle, we can move this code into a module (dependent on containerizer modules landing) and from there, move it into it's own repo
Attachments
Issue Links
- is related to
-
MESOS-3709 Modularize the containerizer interface.
-
- Accepted
-