Details
Description
Looks like there is an unintentional ordering dependency between linux/capabilities isolator and docker/runtime isolator.
For the command task case, since both isolators set ContainerLaunchInfo.command. When merging ContainerLaunchInfo.command, docker/runtime isolator assumes its command is before linux/capabilities isolator's command because 'mesos-execute' should be used as argv[0].
We should try to eliminate this dependency.
Attachments
Issue Links
- relates to
-
MESOS-7643 The order of isolators provided in '--isolation' flag is not preserved and instead sorted alphabetically
- Resolved